Reacting to the future of application architecture
summary
Argues that reactive architecture—grounded in the Reactive Manifesto and illustrated with bee behaviors—delivers responsiveness, resiliency and elasticity using concrete patterns: event sourcing with CQRS, sharding, back pressure and circuit breakers, actor or Vert.x/Verticles models, and frameworks like Akka, RxJava, Spring Reactor and MicroProfile reactive messaging. Cites Verizon results: +1.6% conversion, page responses cut, running on 1/8 the infrastructure and deployments shrunk from 4–8 hours to ~30 minutes, claiming clearer developer productivity gains (20–40%).
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:50Evolution of software
- 2:28Bees and Software Link
- 3:28Food Foraging
- 5:15Long Live the Queen
- 7:13Bees at War
- 9:11Reactive Manifesto
- 13:02Reactive programming vs Reactive systems
- 16:33Domain Driven Design (DDD)
- 18:26Asynchronous Communication
- 19:43Event-Sourcing/CQRS
- 21:36High Availability / Eventual Consistency
- 23:22Sharding
- 24:38Back Pressure
- 25:32Bulkheading
- 26:47Circuit Breaking
- 28:40Reactive Frameworks
- 29:57Actor Model
- 32:16Real World Example -Verizon
- 35:32What Can You Do?
related talks
01h 42mWhat is a Reactive Application?
54mReacting to an Event-Driven World
27mFour Principles of Reactive Architectures
10mInterview on Reactive Applications with Martin Thompson, Todd Montgomery & Viktor Klang
47mThe Rise of Reactive Microservices
41mThe Promise of Event Driven Programming with Fast Data
01h 15mApplying Reactive Programming to Existing Applications
44mDeath to Latency: Building Reactive, Cloud Native Apps with Akka NET