Netflix JavaScript Talks – Async JavaScript with Reactive Extensions




Netflix JavaScript Talks – Episode 1
Async JavaScript with Reactive Extensions

In this talk, you’ll learn how Netflix uses the Reactive Extensions (Rx) library to build responsive user experiences that strive to be event-driven, scalable and resilient. Learn the power of the Observable and how we’ve simplified our lives through the ability to filter, aggregate, compose and project data streams.

Join us while we discuss how Netflix uses Rx to:
– Declaratively build complex events out of simple events (ex. drag and drop)
– Coordinate and sequence multiple Ajax requests
– Reactively update the UI in response to data changes
– Eliminate memory leaks caused by neglecting to unsubscribe from events
– Gracefully propagate and handle asynchronous exceptions

Original source


17 responses to “Netflix JavaScript Talks – Async JavaScript with Reactive Extensions”

  1. I don't get the "I haven't unsubscribed from an event stream in five years" comment. In the drag & drop example, the mouse-down subscription is presumably part of some widget. When you dispose of the widget, in his example you would leak the subscription. Only the mouse-move and mouse-ups subs are automatically disposed. How can he avoid unsubscribing from mouse-down? He says you listen forever, but that's not usually the case, as widgets come & go.

  2. Awesome task, one question: Are Rx Obs better/more flexible than promises or do both have a right to live ? I would say promises are great for one-time async operations like to fetch a Json file or something and, of course, to use ES6 generators to abstract the then away using yield which is not so easy with Obs, isn't it ? I'm just a bit confused because the whole world is talking about promises right now but the rx Obs look kind of better, but maybe I miss hte point about promisese… =/ Would be nice if somebody could clarify that a bit =)

Leave a Reply