Bringing Reactive Programming to Java and Microservices
summary
Reactive programming here means building non‑blocking asynchronous Java services using the Reactive Streams spec (Java 9) and implementations like Reactor, RxJava and Vert.x; Spring WebFlux adopts Reactor core and exposes Mono/Flux publishers with operators, plus Netty as a non‑blocking server. The talk shows the Java evolution (threads → CompletableFuture → reactive streams), explains back pressure and subscription flow (subscribe → request → onNext/onComplete/onError), claims end‑to‑end reactive dependencies let a fixed small thread pool serve far more concurrent requests, and warns of a real learning curve and limited value for plain CRUD apps.
AI-written summary · about
chapters (12)
- 0:00Introduction to reactive Java
- 2:29Reactive manifesto principles
- 5:21Traditional API limitations
- 7:06Event loop and non-blocking
- 10:15Back pressure explained
- 11:40Evolution of Java concurrency
- 13:25Reactive streams specification
- 16:37Reactive streams entities
- 18:22Spring WebFlux overview
- 20:29Reactive controller examples
- 21:56Reactive dependencies
- 22:37Benefits and considerations
related talks
41mThe definite guide to reactive programming in Java
52mReactive for the Impatient - A Gentle Intro to Reactive Java
45mGoing Reactive - An Introduction to Reactive Programming
39mReactive for the Impatient (A Gentle Intro to Reactive Java)
47mReactive Spring
41mFrom Imperative To Reactive
49mReactive Spring
01h 28mIntroduction to Reactive Programming
