The reactive landscape
summary
Argues that “reactive” is three things — Reactive Systems, Reactive Programming, and Reactive Streams — and shows Vert.x as a toolkit that implements them: a per-CPU single event loop per CPU, an asynchronous JDBC + WebClient demo that inserts products, calls a pricer via the Vert.x event bus (or HTTP), and pushes updates to browsers over SockJS/WebSocket bridges. Demonstrates backpressure via Reactive Streams (batching rows, request(n)), runs in the demo without crashing, and warns blocking calls must be offloaded to worker pools.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:47What is reactive
- 3:40Reactive landscape
- 5:39Clements story
- 10:08Way of Systems
- 12:25Stage
- 13:08synchronous development model
- 15:38synchronous and blocking
- 20:00reactive programming
- 22:01reactive extension
- 25:33synchronous operation
- 27:41Nested callback
- 29:34Lazy consumer
- 33:29Back pressure
- 34:41Vertex
- 36:36Evenbus
- 40:41Bridge
- 42:06Demo
- 44:18Reactive systems
- 45:45Questions
