Reactive Programming in Node
summary
Defines RxJS observables as lazy push streams, demonstrates creation, interval/take, merge vs concat and node-specific fromEvent/denodeify operators, and shows Netflix moving to reactive nested conditional and parallel execution to cut client requests. Describes a RabbitMQ-backed metadata pipeline that maps naturally to streams, claims easier concurrency, cancelable subscriptions, and simpler error paths, and notes surprising costs: steep learning curve, breaking RxJS API changes, and cases where single-event overhead makes observables overkill.
AI-written summary · about
chapters (5)
related talks
37mStreaming and event-based programming using FRP and RxJS
28mReactive all the Things
47mReactive Programming in Angular with RxJS
28mWatch out: observers are here to stay
28mReactive Programming Demystified Drink the Kool-Aid
27mEmbrace Reactive Programming in React and Vue with RxJS
43mReactive JavaScript at Netflix, Microsoft and the World
21mReal-Time Stream Processing with Reactive-Extensions (RX)
