CQRS and Event Sourcing: May the Event Be with You
summary
Presents using CQRS together with Event Sourcing in Symfony to create an immutable event log that isolates integration pain and allows teams to replay and rebuild system state after production bugs. Describes a Symfony implementation using subscribers/listeners, a provider/manager split, and storage options (RDBMS, Dynamo/Cassandra), and warns about pitfalls such as missing event data and external-query drift (e.g., exchange rates). Describes a proprietary Symfony audit bundle (not open source) used in production for logging, testing and onboarding.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:15CQRS and Event Sourcing
- 4:18Modern app problems
- 6:25Event Sourcing intro
- 9:15Immutable events
- 11:45Event Sourcing benefits
- 13:32Read/write split
- 16:01Implementation challenges
- 18:08Audit Team Bundle
- 20:44CQRS with Event Sourcing
- 22:09Event naming rules
- 23:32When to adopt
- 24:14Conclusion
related talks
47mFrom C to Q, One Event at a Time: Event Sourcing in Pictures
49mCQRS and Event Sourcing explained
17m7 Reasons why your microservices should use Event Sourcing & CQRS
01h 25mBuilding microservices with event sourcing and CQRS
46mMicroservices Data Patterns: CQRS & Event Sourcing
30mEventSourcing and CQRS — The Introduction That Was Missing
43mAdding Event Sourcing to an existing PHP project (for the right reasons)
47mCQRS and Event Sourcing on Steroids: Lessons Learned with Spring & Axon