Farewell Any - Unit, welcome Akka Typed!
summary
Akka Typed replaces untyped actors with explicit protocols: message types are a sealed ADT, each request carries an explicit typed ActorRef[T] reply address, and cross-actor replies require message adapters, shown in a working account transfer example where withdraw/deposit replies are adapted and the transfer prints “transfer done.” Behaviors replace receive, support synchronous checks via the behavior test kit, and supervision defaults to stop (supervise(...).onFailure(...) lets you resume). Typed and untyped actors interoperate via adapter conversions.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:50The Actor
- 2:15The Behavior
- 3:30Protocol
- 4:47Implementation
- 7:20API Changes
- 8:39Behavior of T
- 11:04Typing
- 16:50Contexts
- 18:38Actor
- 24:34Message Protocol
- 25:28Friendly Competition
- 26:19Coexistence
- 28:54Supervision
- 30:44Calculator
- 34:19Conclusion
- 35:09Next
- 35:19API may change
- 36:14Questions
- 38:14Union Type
related talks
51mAkka Typed: so strong typing doesn't remain dead letter
42mNext generation message driven systems with Akka
38mFresh from the Oven: Akka gets Typed
47mNetworks and Types — the Future of Akka
45mTaming Distribution: Formal Protocols for Akka Typed
35mOne year with Akka 2.6
32mAdopting Actors... an epic tale of loss and learning
22mActing Lessons for Scala Engineers with Akka and ZIO