Event sourcing
summary
Event sourcing stores an immutable log of deltas instead of current state so account balances are derived by replaying events; example builds a banking app that regenerates any past state. Pattern credited to Greg young and oody DeHaan; databases use it internally — MongoDB uses an MongoDB oplog for replication that secondaries replay. Practical cost is replay time, mitigated by snapshots plus replay. Combine with CQRS to separate write model and read model and use eventual consistency on secondaries.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:08Event Sourcing in Command Query Responsibility Segregation
- 2:58Temporal Queries
- 5:26Problem with Event Sourcing
- 6:25Dual Entry Accounting
related talks
52mEvent Sourcing – the what, why & how
46mEvent Sourcing: Superpower or super pain?
52mEvent Sourcing for the Cloud Developer
51mThings I Wish I knew Before I Started with Event Sourcing
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture
01h 01mEvent Sourcing for practice
32mEvent Sourcing in Laravel
48mEvent Sourcing - what could possibly go wrong?