Event Sourcing and CQRS
summary
Builds a football-league scoreboard by storing every game as an immutable event and using Lagom Persistence with Akka Persistence to emit and replay those events; events land in a Cassandra journal and MySQL read-side via a projection that stores a processing offset so replays resume correctly. Demonstrates command→event→state handlers, event tagging, cluster sharding for a single-actor-per-key guarantee, and snapshots every ~100 events to bound replay time; demo shows the MySQL table populated from the event stream.
AI-written summary · about
chapters (36)
- 0:00Introduction
- 0:28Example
- 1:05Why I dont use a relational database
- 2:34Scaling
- 3:48Destructive Operations
- 6:08Cargo Tracking
- 7:37Unlearning
- 9:07DomainDriven Design
- 10:54What is an Event
- 12:30How do we implement this
- 14:29Code
- 14:45Aggregate
- 16:45State
- 17:41Persistent Entity
- 18:13Command Handlers
- 19:17Persistence
- 19:48Validation
- 20:26Cancellation
- 21:26Event Handler
- 24:47Service Describing
- 25:08Demo
- 28:42Cluster Carding
- 30:25Trance
- 31:28Relational Approach
- 31:59Scalability
- 32:37Efficient
- 33:19Event Sourcing
- 34:13Continuous Read
- 37:25Projections
- 39:14Stream Events
- 39:48Scala frameworks
- 40:47Fancy QRS
- 41:50Eventuate
- 43:28Rethinking
- 45:42Un unlearn
- 46:29Questions
related talks
42mCQRS and Event Sourcing with Lagom
49mCQRS and Event Sourcing explained
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
01h 25mBuilding microservices with event sourcing and CQRS
48mEvent Sourcing - what could possibly go wrong?
43mKey-Value, Event-Sourcing, Cqrs, Pub/Sub as a Service, Java, Javascript
52mEvent Sourcing for the Cloud Developer
45mThe Practical Road towards CQRS and Event Sourcing