How Events Are Reshaping Modern Systems
summary
Argues that event-driven design yields autonomous, loosely coupled services and demonstrates a working Akka-based demo: three actors (orders, inventory, payment) wired as a process manager that publishes events to an event stream, persists events with the built-in LevelDB journal, and replays them to rehydrate state on restart. Explains concrete distinctions between commands and events, shows how event sourcing provides durable audit logs and time travel, and shows the demo successfully recovers state and drives eventual consistency across services.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 0:55Why Events
- 2:45Why Now
- 4:48Why Legacy
- 5:52EventDriven Architecture
- 6:54What is an Event
- 9:05The Event Loop
- 12:53EventDriven Microservices
- 16:26Using Events as an Integration Fabric
- 19:07Two Embraces
- 19:30Consistency
- 20:13Past vs Present
- 22:36Events
- 23:16DomainDriven Design
- 24:34Mind the Facts
- 24:52Use Events
- 26:41Commands vs Events
- 28:01Events Define the Bounded Context
- 29:16The Code
- 32:07Actor Model
- 33:53Inventory Logic
- 34:43Receive Logic
- 39:46Scaffold
- 40:22Factory
- 40:53Create Order
- 42:20Persistence
- 51:12Rerun
- 51:57Reactive Micro Systems
related talks
31mDemystifying Event-Driven Architectures
48mEvent-Driven Architecture – Benefits and Pitfalls
56mEvents on the outside, on the inside and at the core
53mDistributed Eventsourcing with Akka
41mThe Promise of Event Driven Programming with Fast Data
01h 00mReacting to an Event-Driven World
51mComplex Event Flows in Distributed Systems
55mAn Introduction to Enterprise Design Events