SCALAZ 8 VS AKKA ACTORS
summary
Compares Akka actors to Scalaz 8 solutions, claiming purely functional code is simpler and far faster: a counter implemented with IORef.modify replaces an actor and runs 10–100x faster in typical contention, with an async queue variant for extreme contention; a parallel workload reduces to one line using Scalaz primitives; a typed function-as-actor (A => B wrapped in IO) is built, composed, and forked successfully; only distributed sharding and clustering remain an Akka win, and the effect system measures up to 200x faster than JVM futures.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:21Answer to the Ultimate Question of Software Development
- 3:24Parallelism
- 4:17Killer Use Cases for Actors
- 4:31Concurrent State
- 5:55Persistence
- 6:47Distributed Compute
- 8:14Can We Do Better?
- 8:55Next-Generation Purely Functional Actor Design
- 17:39Scalaz 8
- 22:50Top Reasons to Choose Actors
related talks
43mThe Design of the Scalaz 8 Effect System
45mSo you want to be an actor? Lessons from implementing the actor model
01h 03mErlang & Akka Actors - A story of tradeoffs
22mActing Lessons for Scala Engineers with Akka and ZIO
54mScala concurrency patterns with Actors
44m10 Lessons From Implementing The Actor Model
52mBuilding Concurrent, Fault Tolerant, Scalable Applications in F# using Akka Net
01h 05mLawful Asynchronous Programming