Reacting to the Future of Application Architecture
summary
Argues that reactive architecture — the Reactive Manifesto’s responsiveness, resiliency and message-driven decoupling — maps to real behaviors (bees' scout dances, guard bees rising from ~11% to ~50%) and to concrete tools: Akka/Lagom (actor model), Vert.x (verticles), Spring Reactor and MicroProfile. Cites Verizon migration: 88% digital traffic, page latency drops, conversion rises, infrastructure down to 1/8, deployments from 48 hours to 30 minutes, developer productivity +20–40%, demonstrating elasticity and fault containment at scale.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:04Evolution of software
- 2:36Bees and Software Link
- 3:31Food Foraging
- 5:34Long Live the Queen
- 7:42Bees at War
- 9:37Reactive Manifesto
- 13:01Reactive programming vs Reactive systems
- 16:25Domain Driven Design (DDD)
- 18:28Asynchronous Communication
- 20:05Event-Sourcing/CQRS
- 22:05High Availability / Eventual Consistency
- 23:54Sharding
- 25:07Back Pressure
- 26:10Bulkheading
- 27:28Circuit Breaking
- 29:34Reactive Frameworks
- 31:08Actor Model
- 32:49Verticles
- 34:18Real World Example -Verizon
- 37:50Why should you care?
- 38:29What Can You Do?
related talks
13mReacting to the future of application architecture
01h 11mReactive Architecture Patterns Debate
55mRethinking Reactive Architectures
41mThe definite guide to reactive programming in Java
12mReactive architecture, design, and programming
48mReactive for the Impatient
03mAm I only streaming? Thinking reactive
15mReactifying your application