• Saturday , 22 September 2018

Netflix JavaScript Talks – Async JavaScript with Reactive Extensions

Code Canyon



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

3d Ocean

Related Posts

17 Comments

  1. Nicholas Xue
    December 27, 2017 at 01:44

    this is great!!!

  2. Mor Win
    December 27, 2017 at 01:44

    Thank you very much! but speak slowly please
    For some reason, all the tutorials of the best developers speaks so fast!
    for goodness sake stop it!

  3. ryanjackson0x
    December 27, 2017 at 01:44

    There are a few factual flaws.
    The speaker talks way too fast.

  4. Tony Brown
    December 27, 2017 at 01:44

    This guys a genius

  5. Joe Buza
    December 27, 2017 at 01:44

    Great presentation. Very easy to understand

  6. Daniel Ram
    December 27, 2017 at 01:44

    Awesome speaker, makes it really clear

  7. Julien Valéry
    December 27, 2017 at 01:44

    very nice rxjs overview with such an enthousiast speaker that make you want to work with

  8. 李毅
    December 27, 2017 at 01:44

    great talk

  9. lucasterable (youtube channel)
    December 27, 2017 at 01:44

    @22:11 retry(3) should be placed after concatAll() to work.

  10. Ivan Kurnosov
    December 27, 2017 at 01:44

    Guys, is the definition for `getJson` from the example at 23:00 available somewhere? Curious how you implemented it to handle errors and support `retry`

  11. birthdayforfrances
    December 27, 2017 at 01:44

    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.

  12. Christopher Probst
    December 27, 2017 at 01:44

    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 =)

  13. Sandy Place
    December 27, 2017 at 01:44

    This is a great intro to RxJS. Well done Jafar.

  14. shay d.
    December 27, 2017 at 01:44

    Very good good presentation, Matthew Podwysocki would be proud. Definitely got across the power of Rx!

  15. Dennis Keller
    December 27, 2017 at 01:44

    Nice job, Matt.

  16. Dan Haywood
    December 27, 2017 at 01:44

    Excellent talk… who knew that Observable and Iterator design patterns were the same thing (more or less)?  Feel a bit dumb that I've only learnt about RX just now.

Leave A Comment

You must be logged in to post a comment.