The definite guide to reactive programming in Java
summary
Explains why reactive is needed for responsive, high‑load systems and demonstrates concrete libraries: RxJava, Project Reactor, Akka Streams. Shows code patterns — filtering a persons list, then flatMap to fetch incomes and combine results — using marble diagrams and a Spring 5 controller returning Mono (single) / Flux (multi). Describes backpressure (request n items to avoid OOM), compares Vert.x event bus and Akka actors for structure, and shows Reactor’s Spring integration; examples compile and run and reduce thread blocking versus callback nesting.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker
- 1:47Why reactive programming
- 6:05Async programming in Java
- 8:12Challenges with callbacks
- 13:34Back pressure explained
- 16:26Reactive Streams in Java
- 20:04Project Reactor vs Akka Streams
- 23:15Blocking vs non-blocking
- 24:58Spring 5 and reactive
- 27:50Event bus and Vert.x
- 30:21Paradigm shift in Java
- 33:47Spring WebFlux demo
- 35:55Actor model with Akka
- 39:42Choosing a framework
- 40:50Summary and recommendations
related talks
52mReactive for the Impatient - A Gentle Intro to Reactive Java
24mBringing Reactive Programming to Java and Microservices
39mReactive for the Impatient (A Gentle Intro to Reactive Java)
45mReactive for the Impatient - A Gentle Intro to Reactive Programming and Systems
48mReactive for the Impatient
45mGoing Reactive - An Introduction to Reactive Programming
30mReactive Applications with rxjava / Spring Reactor
47mReactive Spring