Networks and Types — the Future of Akka
summary
Akka rewrites actors around a typed API where behaviors compose and messages are a protocol type, coexisting with classic actors for migration; supervision is applied by wrapping behaviors, lifecycle events are separate signals, and the receptionist replaces brittle string-based actor selection with typed service keys. The new remoting (Artery) reports 1 million messages/sec and a flag yields 10x performance over old transport; TLS, compression and stream-integrated flow control are implemented and running.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:44Clustering
- 29:23Message Adapter
- 29:50Ask Pattern
- 32:08Life Cycle
- 38:46Mutable Behavior
- 39:50Supervision
- 41:30The Downsides
- 42:09Flow Control
- 45:04Tracing Monitoring
related talks
37mAkka Present and Future
50mNext Generation Actors With Akka
01h 14mAkka.NET: The Future of Distributed Programming in .NET
35mOne year with Akka 2.6
38mFresh from the Oven: Akka gets Typed
17mYou asked for it, you got it: type safe Actors
42mFarewell Any - Unit, welcome Akka Typed!
39mAkka.net: The actor programming model