Reactive Design Patterns
summary
Argument: reactive systems demand different design — partition state, decouple components, and make communication message-driven. Concrete claims: elasticity, resilience and responsiveness follow if components are single‑responsibility and communicate asynchronously. Tools and implementations: Akka primitives (Futures, a built‑in circuit breaker, Akka Persistence) and persistent sagas are shown; sagas use safe points, compensating actions and idempotent operations. Evidence: Netflix’s 6× diurnal load swing motivates scaling, and a working Akka‑persistence saga implementation demonstrates feasibility.
AI-written summary · about
chapters (8)
- 0:00Introduction to reactive
- 1:07Principles of reactivity
- 4:58Resilience and responsiveness
- 9:20Message-driven communication
- 12:40Component pattern analysis
- 23:30Circuit breaker pattern
- 27:36Request-response pattern
- 32:00Saga pattern for transactions
related talks
55mRethinking Reactive Architectures
59mSucceeding at Reactive Architecture
42mReacting to the Future of Application Architecture
44mArchitectural Patterns of Resilient Distributed Systems
30mReacting to the future of application architecture
54mReacting to an Event-Driven World
34mReactive Architecture
39mReacting to an Event-Driven World