Taming Distribution: Formal Protocols for Akka Typed
summary
Proposes using Akka Typed plus parameterized ActorRefs and effect-tracking HList-like types so the compiler enforces the ordering of distributed message exchanges. Builds a prototype DSL (processSL) with ops like send, read, fork and flatMap that accumulates a type-level list of effects, demonstrates a payment+audit workflow where the compiler rejects out‑of‑order or missing steps, and models server loops and forks. Prototype achieves static safety but gives very verbose type errors and remains researchy, not production-ready.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:15The book is out!
- 10:35Akka Typed Receptionist API
- 12:09with Unregister support
- 14:46Cluster Receptionist
- 16:26Messages for a payment system
- 17:56Akka Typed crash course
- 19:41First actor: do the audit
- 20:58Second actor, do the payment
- 22:31Third actor: orchestration of the process
- 25:34Which steps shall be done?
- 26:52Akka Typed Session: protocol definition
- 27:56First process: do the audit
- 30:19Second process: do the payment
- 30:49Third process: orchestrate and verify
- 33:19Effect tracking
- 35:56List of effects
- 36:33Sequencing actions
- 39:57and there are loops as well
related talks
38mFresh from the Oven: Akka gets Typed
17mYou asked for it, you got it: type safe Actors
47mNetworks and Types — the Future of Akka
50mNext Generation Actors With Akka
42mFarewell Any - Unit, welcome Akka Typed!
37mAkka Present and Future
35mOne year with Akka 2.6
41mTowards language support for distributed systems