Thirst Quenching Streams for the Reactive Mind
summary
Compares concrete Java implementations (Project Reactor, RxJava 2/3, Vert.x, Akka Streams, MicroProfile, RSocket, OSGi push streams), explains the Reactive Streams API (Publisher/Subscriber/Subscription/Processor) and the TCK requirement, and demonstrates an Akka Streams CSV file-watcher built with Alpakka that runs locally (and can be deployed to IBM Cloud/Vert.x/Kubernetes). Emphasizes back pressure as the key problem, notes Flux/Mono vs Flowable/Observable differences, and highlights RSocket v1.0 as a lower-latency, lower-resource protocol.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:01Thirst-Quenching Streams for the Reactive Mind
- 6:49Reactive Concepts
- 16:59Rx Marble Diagram: Mapo
- 19:26Concurrency vs Parallelism
- 20:55Streams Processing models: Push vs Pull
- 26:31Pull downstream initiates and pulls from upstream
- 32:40Reactive Streams: Java interfaces
- 48:04Micro Profile Reactive Messaging
- 51:28The Reactive Foundation and RSocket
- 52:53The Reactive "primitives"
- 58:25IBM Cloud
related talks
49mThirst Quenching Streams for the Reactive Mind
44mThirst-Quenching Streams for the Reactive Mind
56mThirst-quenching Streams for the Reactive Mind
32mThirst-Quenching Streams for the Reactive Mind
56mThirst-Quenching Streams for the Reactive Mind.
39mReactive for the Impatient (A Gentle Intro to Reactive Java)
52mReactive for the Impatient - A Gentle Intro to Reactive Java
41mThe definite guide to reactive programming in Java
