Tom Hughes-Croucher, creator of Jetpacks for Dinosaurs (and formerly of Yahoo), provides out a total bargain of techniques on using Node.JS to make streaming options in this discussion from HTML5 Dev Conf.

Covering whatever from traffic jams, to issues with pipeline, to API usage, this talk is positive to have a little something for anyone using Node.JS to stream. In addition to, you get to see a dinosaur placing on a jetpack.

For a lot more from HTML5DevConf, go to


8 thoughts on “Dealing with Node.js to Produce Terrific Streaming Professional services”

  1. I appreciate the background on some of the Node infrastructure and what the process loop is, but I have to say that a scripted talk or at least one that is frame worked would be much more insightful for this. Essentially, you brought up a lot of the "gotcha's" and issues that come up when trying to implement stream services for data, etc. And then a very long explanation of cache tuning for the que…but I don't see a break down of "WHAT THE BEST PRACTICES FOR BUILDING STREAMING SERVICES" are. A simple bullet point or top 10 would be much more fruitful. When trying to consume a lot of this information quickly, it's hard to slow down my own processing power to watch a presenter debug, presumably pre-written snippets of code, in relation to the exact topic they are talking about. Along with switching back and forth among many screens of info, but in no particular order. ie: when buffers are over run, is there a simple and quick way to stop the spigot from running at the head, and mark the last received piece of data so that when the spigot is turned back on with the tuned cache, the data delivery picks up right where it left off? Is there a way to offload the incoming data to a database so as not to take up resources on the server's main memory and avoid "service unavailable errors"? a practical example would be helpful as well, with perhaps a bare bones skeleton of working code showing code in node.

  2. Oh no! Never use += with strings, . It is drastically faster to build an array of strings with push, then .join('') at the end. V8 is utterly terrible at += with strings.

  3. i don't know if this is being pedantic? you still have a bug at 09:48… parts are only increased after calling finish. no guarantee that 'parts' will be equal to 2 when the second 'finish' is called. all in all – nice presentation.

Leave a Reply

Your email address will not be published. Required fields are marked *