Implementing Microservices with Scala and Akka
summary
Argues that practical microservices map to event-sourced bounded contexts rather than arbitrary line counts, implemented with Scala and Akka actors, CQRS and an event journal per service. Demonstrates a registry, a topics (Rapids) pub/sub bus and rivers that filter events, a process manager that creates a forum in a separate service, and a working end-to-end demo where create-product triggers discussion-started across services. Cites 12–20 ms REST latency and messaging throughputs from tens of thousands to millions/sec.
AI-written summary · about
chapters (16)
- 0:00Introduction and books
- 0:59The danger of extremes
- 4:21Monoliths vs microservices
- 6:31Defining microservice size
- 8:52DDD bounded context approach
- 12:51Ubiquitous language cohesion
- 17:20Event-driven architecture
- 22:35Rapids, Rivers, and Ponds
- 25:59Service interactions
- 27:53Reactive principles in DDD
- 32:06Distributed system demo
- 34:34Code walkthrough
- 40:43Process managers
- 44:16Running the demo
- 48:37CQRS implementation
- 50:48Q&A and conclusion
related talks
44mLong-lived microservices
48mChallenges in Implementing MicroServices
49mChallenges in Implementing Microservices
41mHow to write microservices in Scala without Akka
58mImplementing Event-driven Microservices
50mChallenges in Implementing Microservices
37mBeyond Microservices: Streams, State & Scalability
48mThe three paths of Scaling with Akka
