From Imperative To Reactive
summary
Argues that imperative code must shift to non‑blocking async and shows a concrete stack: Reactor types Flux and Mono, Reactive Streams for backpressure via Reactive Streams, and integration into Spring 5 as Spring Web Reactive Milestone: REST first. Demonstrates converting from Java 8 streams and CompletableFuture, that nothing executes until a subscriber subscribes, per‑item Jackson serialization to avoid blocking, runtime support with Netty/Tomcat/Jetty/Undertow, and testing with Reactor test utilities (TestSubscriber).
AI-written summary · about
chapters (33)
- 0:00Intro
- 0:52Concurrency
- 1:31Conventional wisdom
- 2:25Cloud deployment
- 2:59Impact on programming model
- 4:06Asynchronous foundation
- 4:40How can I become asynchronous
- 5:33Java Asynchronous API
- 5:51User Repository
- 6:07TryCatch
- 7:52completable
- 8:09completable future
- 8:49return list of users
- 9:02a completable future
- 9:53too many
- 10:39void API
- 10:50asynchronous return values
- 11:30asynchronous return types
- 12:24stream abstraction
- 12:55stream API
- 13:31reactive libraries
- 16:15flux
- 18:04back pressure
- 19:22flow
- 20:33Publisher
- 23:10Streams Example
- 24:47Unsubscribe
- 25:38Give me 2 at a time
- 26:18Any questions
- 26:36What does this mean
- 29:13Reactive Web Engine
- 30:58Testing
- 36:53ThreadLocal Variables
related talks
24mBringing Reactive Programming to Java and Microservices
47mReactive Spring
52mReactive for the Impatient - A Gentle Intro to Reactive Java
39mReactive for the Impatient (A Gentle Intro to Reactive Java)
49mReactive Spring
41mThe definite guide to reactive programming in Java
48mReactive for the Impatient
53mReactive Mythbusters With Reactor