Hidden gems and traps that you probably didn't think of using Event Sourcing
summary
Shows a concrete Spring Boot + Axon Framework demo: a shopping‑cart service that emits events to Axon Server, replays history to rebuild state, and creates a new projection that backfills from about 1.5 million events so a new feature immediately gets historical data. Claims: event store is append-only event store (immutable events), long aggregates need snapshots, and you must implement distinct command/event/query routing semantics and choose a broker tailored for those patterns. Demo works end‑to‑end and reveals auditing and debugging benefits and practical traps.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:42Storytime
- 2:35The Ledger
- 7:15Distributed Systems
- 7:47Pain of Implementing Arrows
- 9:51EventDriven Architecture
- 17:11Shopping cart example
- 21:23Demo
- 34:59New Features
- 37:27Real Estate
- 38:40Shopping Cart
- 40:42Why Event Sourcing
- 41:17Commands and Queries
- 43:14Routine Patterns
- 45:35Storing
- 47:09Degradation
- 48:28Summary
related talks
45mThe Practical Road towards CQRS and Event Sourcing
50mThe harsh reality of Event Sourcing - mitigated with Spring and Axon on Tanzu Application Platform
47mGive Your Application Memories
47mCQRS and Event Sourcing on Steroids: Lessons Learned with Spring & Axon
56mAn Abridged Guide to Event Sourcing
31mThe Power of Event-Driven Systems without Burning your Hands or Budgets
43mFunctional and Reactive Event Sourced Applications
29mEVENT SOURCING IN AKKA PERSISTENCE