An Architecture with CQRS and Event Sourcing
summary
Describes a concrete CQRS + event sourcing stack: events stored as JSON in Postgres JSON event store, projections materialize denormalized views and are rebuilt by replay historical events or by using savepoints/snapshots (Greg Young suggests snapshots at ~1,000 events). Uses Spring 4.2 event listeners to cut boilerplate, can push projection updates over Kafka for scale, and cites an e‑commerce case that replays years of events to target users who added then removed items. Reports sub‑100ms projection lag in practice.
AI-written summary · about
chapters (11)
- 0:00Introduction to CQRS and Event Sourcing
- 1:06Where CRUD still makes sense
- 8:37Introduction to event sourcing
- 11:47CQRS and event driven architecture
- 18:07Traditional vs event sourced architecture
- 22:19Projections and denormalized data
- 31:16Spring and event sourcing
- 37:16Advanced projection scenarios
- 43:00Benefits of event sourcing
- 49:26Cons and challenges of event sourcing
- 53:16Q&A session
related talks
01h 25mBuilding microservices with event sourcing and CQRS
49mCQRS and Event Sourcing explained
48mEvent Sourcing - what could possibly go wrong?
52mEvent Sourced Transformation in Financial Systems
43mEvent Sourcing dealing with an eventful past
52mEvent-driven vs event sourcing: what's really the difference?
47mFrom C to Q, One Event at a Time: Event Sourcing in Pictures
30mEventSourcing and CQRS — The Introduction That Was Missing