8 Akka anti-patterns you'd better be aware of
summary
Eight concrete Akka mistakes and how they break systems: leaking mutable state (use immutable messages and query/answer patterns), flat actor hierarchies instead of supervision (use supervisors and backoff supervisor for retries), running many actor systems (share dispatchers or use a separate dispatcher for blocking work), synchronous/blocking calls (use futures + pipe pattern), synchronous logging (use async appenders), default Java serialization (switch to protobuf/thrift), routers for hotspots, and tune threads to real hardware.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:50Who am I
- 2:49Global mutable state
- 4:15Actors
- 6:59Flat actors
- 10:42Too many actor systems
- 13:37Logging the wrong way
- 17:23Out of touch with hardware
- 27:33Wasted time
- 33:38Questions
related talks
29mTHINGS I WISH I KNEW WHEN I STARTED WITH AKKA
50mNext Generation Actors With Akka
27mFour Principles of Reactive Architectures
47mNetworks and Types — the Future of Akka
45mSo you want to be an actor? Lessons from implementing the actor model
37mBeyond Fault Tolerance
47mTop 10 Event-Driven Architecture Pitfalls
42mTesting Akka actors in smart way