Welcome + Opening Remarks
summary
Defines reactive systems as four practical properties: always responsive, scale up and down under load to handle spikes and save money, and stay responsive when parts fail using asynchronous messaging for loose coupling. Gives an operational motivation: tired of weekend outage escalations, cites a past environment with 50,000 servers at ~10% utilization, and celebrates being able to kill nodes and the application keeps running as proof the approach works.
AI-written summary · about
related talks
42mReacting to the Future of Application Architecture
45mReactive for the Impatient - A Gentle Intro to Reactive Programming and Systems
34mReactive Architecture
12mReactive architecture, design, and programming
01h 11mReactive Architecture Patterns Debate
50mThe reactive landscape
03mAm I only streaming? Thinking reactive
55mReactive Systems: 21st Architecture for 21st Century Systems