What can Lagom do for you?
summary
Shows concrete features and demos: Lagom sits on Play and Akka Persistence and enforces single-writer via cluster sharding, demonstrates entity passivation, event sourcing + CQRS with a persistent entity API, and a read side using JDBC/Slick read-side with exactly-once offset tracking (offset and DB write in one transaction). Live demo boots Postgres and Kafka, wires ServiceCall APIs to WebSockets and topics, shards tags (example 10 shards) and generates clients — useful if planning Akka-based microservices with built-in persistence and sharding.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:36Agenda
- 2:43Dev Tools on Development Environment
- 6:23Temporal Dependency
- 17:59Restart Source
- 22:55Demo
- 24:57What Happens if I Apply the Event and It Fails To Persist
- 27:17Event Processor
- 38:00Pub / Sub
related talks
42mCQRS and Event Sourcing with Lagom
50mLagom: a CQRS Framework for Next Monday — Good Idea or Not?
42mLightbend Lagom: Microservices Just Right
54mLightbend Lagom: Microservices "Just Right"
52mEvent Sourcing and CQRS
55mExperience report on using Akka in production: pitfalls and rewards
46mState or events? Which shall I keep?
48mThe three paths of Scaling with Akka
