The Good, The Bad and The Ugly - An Event Sourcing Retrospective
summary
A retrospective on a 2012 migration from CQRS to Event Sourcing that details technologies and operational practices used: an event store with relational projection databases, custom projection services, partitioning, and AWS autoscaling. It covers benefits (scalability, auditability, replay-to-point-in-time, separate audit trails) and pains (millions-of-events projection rebuilds, conflict/merge issues for concurrent edits, need for blue‑green side‑by‑side projections and careful engineering tradeoffs).
AI-written summary · about
chapters (9)
- 0:00Event sourcing intro
- 3:10Traditional DB vs event sourcing
- 7:26Scalable projections
- 12:42Business decisions from events
- 18:01Domain complexity
- 24:19Large transactions
- 29:16Event sourcing versioning
- 33:31Archiving and compliance
- 35:39Conclusion
related talks
40mEvent Sourcing: the good, the bad and the complicated
48mEvent Sourcing - what could possibly go wrong?
52mEvent Sourcing: deep dive
47mFrom C to Q, One Event at a Time: Event Sourcing in Pictures
49mCQRS and Event Sourcing explained
46mMicroservices Data Patterns: CQRS & Event Sourcing
01h 25mBuilding microservices with event sourcing and CQRS
52mEvent Sourcing – the what, why & how