Reactive Microservices with Akka and Docker
summary
Demo builds two microservices — a user service and a chat service — packaged as Docker images via sbt-native-packager, using akka-http for APIs, Cassandra as the journal and Akka Persistence for event sourcing; a persisted user survives container restart and a cluster singleton migrates when the oldest node dies. The chat service subscribes asynchronously to user changes via Server-Sent Events with reconnect using Last-Event-ID, applies events into its own store, and the whole setup uses cluster singleton and Akka Persistence and runs successfully in the demo.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:27What is a Microservice
- 4:00Communication
- 7:39Demo
- 8:50Archive GP
- 9:49User API
- 11:33Define your project
- 17:20HTTP marshalling
- 18:00JSON marshalling
- 18:40Persistence
- 23:02Contact Points
- 24:40Networking
- 26:33Application Comp
- 26:58Seed Notes
- 29:47Singletons
- 33:13Collaboration
- 35:32Publishing user events
- 38:58Running user module
related talks
57mBuilding Stateful Clustered Microservices with Java, Actors, and Kubernetes
44mLong-lived microservices
48mThe three paths of Scaling with Akka
54mJava based microservices, containers, Kubernetes - how to
44mAkka post-mortem in a microservice architecture
55mExperience report on using Akka in production: pitfalls and rewards
30mReactive Microservice framework for...
22mRapidly Developing Microservices with Node js and Docker