Event Sourcing for practice
summary
Event Sourcing as an architectural pattern for data persistence: instead of storing entity state, store the sequence of events and rebuild state on demand. Covers benefits such as auditability, fixing bugs retroactively, maintaining complex consistency and gaining scalability, and explains this alternative approach to persistence in practical terms.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:03Classic architecture: Read
- 2:26Classic architecture: Write
- 3:03Classic architecture: Coordination
- 5:30The real world is a stream of events
- 9:51Journal is strictly sequential
- 11:46Commands
- 14:35Command Processing
- 16:08No transactional context
- 22:06Entity granularity
- 23:36Sharding (a.k.a partitioning)
- 25:04Putting it together
- 29:19Snapshots
- 30:40Event representation
- 32:29Schema Evolution (2)
- 41:43Consequence: Audit trail
- 43:19Natural place for raw data
- 47:52Consequence: Simpler consistency within an aggregate
- 50:36Consequence: Explicit cross-entity coordination
- 51:13Saga: Choreography
- 51:59Saga: Orchestration
- 52:18Consequence: distributed programming model
- 54:27CQRS: Command Query Responsibility Segregation
- 55:14Event Sourcing is a tactical decision
- 59:11Further reading
related talks
52mEvent Sourcing – the what, why & how
52mEvent Sourcing for the Cloud Developer
10mEvent sourcing
48mEvent Sourcing - what could possibly go wrong?
39mEvent Sourcing with Elixir
51mThings I Wish I knew Before I Started with Event Sourcing
51mMicroservices Data Patterns: CQRS & Event Sourcing
49mWhy Event Sourced Systems Fail