Event Sourcing: the good, the bad and the complicated
summary
Built a working code review marketplace prototype (not live for legal reasons) using event sourcing plus CQRS: aggregates, an immutable event stream, projectors and process managers drive behavior, and external tools like GitHub Fabricator Bitbucket GitLab Stripe Mailgun integrate with retries. The claim is that event sourcing fits process‑oriented OLTP, it forces designing six artifacts per feature, scales by async commands, survives outages, and a two‑developer team can make it work using phosphorus and only Posterous.
AI-written summary · about
chapters (8)
- 0:00Start
- 10:30Event Storming
- 21:31The Event Stream
- 26:46Recap
- 27:05Command Handler
- 30:26Design the Aggregate Method
- 37:27Executing Business Logic outside the Aggregate
- 39:36Use Case Scenario
related talks
36mThe Good, The Bad and The Ugly - An Event Sourcing Retrospective
52mEvent Sourcing for the Cloud Developer
44mEvent Sourcing - You are doing it wrong
48mEvent Sourcing - what could possibly go wrong?
49mCQRS and Event Sourcing explained
52mEvent Sourcing – the what, why & how
39mEvent Sourcing made Simple
52mEvent Sourcing: deep dive