CQRS and Event Sourcing with Lagom
summary
Lagom presents microservices implemented as CQRS plus Event Sourcing: commands generate events stored in a Cassandra journal (with snapshots) and events update separate read-side tables which can be replayed to rebuild state. The demo builds a port inspection service using Lightbend technologies (Lagom/Play/Akka Persistence), Docker for local clusters, and supports SQL read stores; it highlights practical complexities around retries, eventual consistency, and startup/service-locator edge cases.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:46CQRS and Event Sourcing
- 4:17CQRS and Event Sourcing in DDD
- 7:19Event Sourcing with events and states
- 10:53Event Sourcing challenges
- 13:24CQRS and ES benefits
- 15:38Lagom design philosophy
- 17:44Lagom framework and languages
- 19:50Lagom tooling
- 21:59In-memory vs persistence
- 23:53Database choices and performance
- 25:02Inspection service
- 28:46Commands events and updates
- 31:22Reading states and replay
- 33:10Event processors
- 35:51Views and reports
- 36:54Complexity and consistency
- 39:04When to use CQRS and ES
- 40:50Practical tips and mistakes
- 41:31Resources and further reading
related talks
50mLagom: a CQRS Framework for Next Monday — Good Idea or Not?
52mEvent Sourcing and CQRS
47mWhat can Lagom do for you?
01h 25mBuilding microservices with event sourcing and CQRS
48mNodeJS Microservices + CQRS + Event Sourcing — Why Do I Do This?
54mLightbend Lagom: Microservices "Just Right"
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
01h 07mAn Architecture with CQRS and Event Sourcing