Event driven development
summary
Covers how task-based UI drives clear commands, how event sourcing stores every change as events (like Git deltas) and how projections and process managers turn those streams into queryable read models and state machines (example: three purchases in a year yields a voucher). Shows a concrete stack: command bus, aggregates producing events, event store, event bus, projections, anti‑corruption layer and queues. Points to a working event‑sourced ticketing system on GitHub that actually sells conference tickets in production.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 4:49What is an event?
- 8:59A CRUD UI
- 9:50A Task Based UI
- 13:58A familiar model
- 14:48Event sourcing example
- 16:30Event sourcing architecture
- 17:48Handling a command
- 21:12Inside the model
- 25:05Handling Events
- 28:42Projections
- 30:38A projection
- 33:08Process managers
- 35:26A Process Manager
- 37:50Event Driven Architecture
- 39:17Cross System Process
related talks
54mThinking in Events
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture
38mEvery Event, Everywhere, All at Once
26mEvent-Sourcing your React-Flux applications
49mEvent-Sourcing your React-Redux applications
54mSo You Want to Build An Event Driven System?
50mAn Introduction to CQRS and Event Sourcing Patterns
34mOperate Heavily Dynamic UIs with RxJS