Building Reactive applications with Reactor and the Reactive Streams standard
summary
Reactive Streams becomes a concrete interoperability layer: a four‑interface spec plus a TCK that lets Reactor, RxJava, Ratpack and others exchange non-blocking backpressure and signals. The stack uses Reactor libraries, RingBuffer (Disruptor) for lock‑free dispatch, Spring Data repositories and Netty/Ratpack for HTTP/websocket delivery; demo wires a service stream into a websocket and merges live + historical events. Teams report millions of events/day, apps running days without GC pauses, and the demo works end‑to‑end as presented.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:14Community and logistics
- 2:19Microservices concept
- 4:46Importance of boundaries
- 6:45Latency and responsiveness
- 10:13Reactive programming
- 13:15Fault tolerance and scale
- 17:39Scaling strategies
- 20:17Inside Project Reactor
- 22:59Fast IO and utilities
- 26:46LMAX disruptor
- 30:51Reactor API overview
- 34:43Callback hell and streams
- 36:38Stream use cases
- 39:06Streams vs containers
- 41:57Combining bus and streams
- 45:58Hot vs cold streams
- 49:24Reactive streams spec
- 52:25Back pressure
- 56:38Subscription model
- 1:01:06Push vs pull mode
- 1:04:05Processors
- 1:06:05Java 8 vs reactive streams
- 1:10:24Industry adoption
- 1:13:30Demo and real-world code
- 1:19:36Specification details
- 1:24:20Future and conclusion
related talks
01h 21mReactive Web Applications
30mReactive Applications with rxjava / Spring Reactor
52mMulti Service Reactive Streams Using Spring, Reactor, and RSocket
29mBuilding Reactive Systems with Reactor
02h 45mReactive Revolution
51mReactor 3, the reactive foundation for Java 8 (and Spring 5)
55mThe Reactive Revolution
58mReactive Spring