Four Principles of Reactive Architectures
summary
Retail betting workloads spike every weekend and the Reactive Manifesto prescribes Responsive, Resilient, Elastic, Message Driven systems that scale and fail locally. Uses Akka actors with 2.5 million actors per GB of heap (actors hold local state, mailbox serializes one-by-one, dispatchers separate blocking work), Akka Streams with backpressure and many source integrations, Akka Cluster for transparent distribution and cluster singletons, proven resilience via the let it crash approach and Erlang’s decades‑long uptime, while Project Loom virtual threads may reduce but not remove the need for backpressure.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 2:00Speaker introduction and context
- 3:26Problems with traditional architectures
- 7:04Reactive manifesto principles
- 9:11What is reactive programming
- 10:38Actor model with Akka
- 14:11Building resilient systems
- 17:00Scaling with Akka cluster
- 19:29Reactive streams and Akka Streams
- 21:56Future of reactive programming
- 24:05Key takeaways and conclusion
related talks
01h 11mReactive Architecture Patterns Debate
01h 42mWhat is a Reactive Application?
44mDeath to Latency: Building Reactive, Cloud Native Apps with Akka NET
44mReacting to the future of application architecture
41mThe Promise of Event Driven Programming with Fast Data
12mReactive architecture, design, and programming
37mBeyond Fault Tolerance
54mReacting to an Event-Driven World