Reacting to the future of application architecture
summary
Argues reactive architecture by example: IBM and Lightbend rebuild Verizon’s platform into a reactive microservice system and deliver concrete wins — conversion rate +1.6%, page latency down and infrastructure cut to 1/8th of previous, deployments from 4–8 hours to ~30 minutes, developer productivity up 20–40%, and task completion from 41 to 27 minutes. Recommends concrete tools and patterns: Akka/Lagom, Play, Vert.x, MicroProfile reactive messaging, event sourcing + CQRS, sharding, backpressure, bulkheading and circuit breakers.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:28Evolution of software
- 2:24Bees and Software Link
- 2:56Food Foraging
- 4:23Long Live the Queen
- 5:49Bees at War
- 6:49Reactive Manifesto
- 9:44Reactive programming vs Reactive systems
- 12:22Domain Driven Design (DDD)
- 13:54Asynchronous Communication
- 15:04Event-Sourcing/CQRS
- 16:22High Availability / Eventual Consistency
- 18:01Sharding
- 19:27Back Pressure
- 20:47Bulkheading
- 21:48Circuit Breaking
- 23:15Reactive Frameworks
- 24:55Real World Example -Verizon
- 26:59Do you care about these?
- 27:37What Can You Do?
- 28:34Links to Learn More
related talks
54mReacting to an Event-Driven World
49mReactive microsystems
59mSucceeding at Reactive Architecture
42mReactive Design Patterns
49mNowadays Architecture Trends, from Monolith to Microservices and Serverless
48mReactive Microservice in Action
47mThe Rise of Reactive Microservices
46mGet Reactive! Programming, Systems, and Microservices