Interview on Reactive Applications with Martin Thompson, Todd Montgomery & Viktor Klang
summary
Claim: modern business systems must be responsive, resilient, elastic because they run 24/7 and can need to scale from a few machines to ~1,000s for spikes like payday. Techniques recommended are message-driven async boundaries, making errors first-class and isolating failures, using metrics to drive autoscaling, and avoiding contention with parallel-friendly algorithms. Examples and provenance: Erlang/telecom patterns (Tandem, Ericsson phone switches) are cited as proven; no demo here, but concrete architecture patterns and operational numbers are given.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:48Core properties
- 3:35Resilience requirement
- 6:08Elasticity and decoupling
- 8:16Message-driven benefits
- 9:39Reactive principles history
related talks
44mReacting to the future of application architecture
27mFour Principles of Reactive Architectures
55mGoing Resilient
51mPatterns for building resilient software systems
54mReacting to an Event-Driven World
01h 03mPatterns for Resilient Architecture
14mCreating tools to cross machines and networks
53mResiliency and Availability Design Patterns for the Cloud