Thirst-Quenching Streams for the Reactive Mind
summary
Compares concrete Java implementations — Reactor (Flux and Mono), RxJava (Flowable vs Observable), Vert.x and Akka — with code showing a Vert.x HTTP server converted to a Flowable that subscribes and returns "hello world". Explains that Reactive Streams defines four interfaces (Publisher, Subscriber, Subscription, Processor) and that backpressure lives on Subscription, arguing the model is pull-centric. Introduces RSocket with four interaction modes and claims it is efficient and backpressure-aware (RSocket request-response), plus notes workshop deployment to Kubernetes/OpenShift.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:12Reactive Concepts
- 6:39Rx Marble Diagram: Map()
- 16:51Concurrency vs Parallelism
- 20:19Reactive Architecture design patterns
- 24:34Streams Processing models: Push vs Pull
- 25:55Push: from upstream to downstream
- 26:26Pull: downstream initiates and pulls from upstream
- 27:41Backpressure
- 32:45Spring Reactor (Pivotal)
- 33:13Reactive Extensions (RxJava)
- 33:33Vert.x (Eclipse Foundation)
- 34:00MicroProfile Reactive Messaging
- 35:02The Reactive Foundation and RSocket
- 37:02The Reactive "primitives"
related talks
01h 01mThirst Quenching Streams for the Reactive Mind
49mThirst Quenching Streams for the Reactive Mind
56mThirst-quenching Streams for the Reactive Mind
56mThirst-Quenching Streams for the Reactive Mind.
32mThirst-Quenching Streams for the Reactive Mind
39mReactive for the Impatient (A Gentle Intro to Reactive Java)
24mBringing Reactive Programming to Java and Microservices
47mReactive Spring