The Zen of Akka
summary
Fourteen concrete Akka rules: use messaging and many small actors with context.spawn to get hierarchy and supervision, avoid actor selection and give descriptive actor names (fetch-worker-1), prefer vars holding immutable collections over val with mutable containers, and never block the default dispatcher — configure a separate blocking dispatcher (thread-pool-executor). Replace Java serialization with Kryo or Protobuf (benchmarks show ~5x+ gains versus Java ser), use after+Future for timeouts, backoff supervisor for DB outages, and respect cluster allow-weakly-up members and convergence.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:10Agenda
- 1:25The Tao/Zen of Programming
- 3:01A 18: One actor is no Actor
- 5:1928: Structure your Actors
- 6:23Name your Actors
- 9:34"Matrix of mutability (Pain)"
- 25:31Backoff Supervision
- 28:03108: Design using State Machines
- 33:24118: Cluster Convergence and Joining CLUSTER PARTY 2016
- 39:14131: A fishing rod is a tool. Akka is a Toolkit.
- 41:56Happy hAkking, Community!
related talks
50mThe Zen of Akka
40mTop Mistakes When Writing Reactive Applications
51mUp up and Out: Scaling Software with Akka
01h 32mFrom Spring + Java to Spring + Akka - A Journey of Discovery
37mAkka Present and Future
32mAdopting Actors... an epic tale of loss and learning
51mAkka Typed: so strong typing doesn't remain dead letter
38mBest Practices in Reactive Application with Java 1.8 and Play