Unraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture
summary
Shows event sourcing implemented with an account example—four events (opened, deposit, withdraw, fee) projected to a balance—and explains event streams, optimistic concurrency and snapshotting tradeoffs. Demonstrates read/write separation patterns (CQRS), when to add async read projections and a message broker, and practical cautions: Event Store DB vs Kafka, the outbox pattern for broker outages, and why Kafka is not suitable as an event store; argues for pragmatic, incremental adoption rather than wholesale rewrites.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:38Event sourcing examples
- 18:50CQRS patterns
- 30:22Event-driven fundamentals
- 36:47Pitfalls and anti-patterns
- 40:20Best practices
related talks
52mEvent Sourcing for the Cloud Developer
48mEvent-Driven Architecture – Benefits and Pitfalls
01h 25mBuilding microservices with event sourcing and CQRS
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
51mMicroservices Data Patterns: CQRS & Event Sourcing
44mEvent Sourcing - You are doing it wrong
31mDemystifying Event-Driven Architectures
46mMicroservices Data Patterns: CQRS & Event Sourcing
