THINGS I WISH I KNEW WHEN I STARTED WITH AKKA
summary
Keep actor APIs immutable: put Props and messages in the companion object so creation and message types are explicit. Avoid hiding business logic in actor state: move business logic into pure functions and test synchronously. Replace complex per-message timeouts and mailbox backpressure with streaming: use Akka Streams for workflows (example: a seven‑step trip cancellation modeled as a stream). Only adopt clustering features (Sharding, Persistence, Distributed Data) when unavoidable—they add deployment, rolling‑update and testing complexity. Also design master/worker boundaries to prevent mailbox blowups.
AI-written summary · about
chapters (18)
- 0:00Akka introduction
- 1:09Props and companion objects
- 2:36Managing state with behaviors
- 4:21Message handling with companions
- 7:21Testing business logic
- 8:16Cancellations with futures
- 10:34Akka pipelines and timeouts
- 13:45Mailboxes for efficiency
- 15:58Master-worker actors
- 17:00Business workflows with Streams
- 18:12Kafka events with Streams
- 20:05Akka clustering
- 21:53Deployment strategies
- 23:24Testing network partitions
- 24:54Debugging and performance
- 26:19Choosing Akka Cluster
- 27:12Caching strategies
- 28:04Final thoughts and best practices
related talks
47m8 Akka anti-patterns you'd better be aware of
45mSo you want to be an actor? Lessons from implementing the actor model
50mNext Generation Actors With Akka
47mNetworks and Types — the Future of Akka
37mAkka Present and Future
27mFour Principles of Reactive Architectures
17mYou asked for it, you got it: type safe Actors
48mReliable messaging in the world of actors