This is an overview of Akka anti-pattern articles. You can think of these anti-patterns as the opposite of Akka best practices – that is, things you should not be doing when using Akka.
Here is also a talk about 8 very frequent anti-patterns out there:
- Shared mutable state
- Flat actor hierarchies / Mixing business logic and failure handling
- Race conditions
- Stateless actors
- Too many actors
- Logging the wrong way
- Being out of touch with the hardware
- Overusing ActorSelection
- Using Java Serialization
Network / Cluster
- Using remoting
- Trusting the network
- Always using the defaults (to be written)
- Using cluster without / with the wrong split-brain resolver (to be written)
Architecture / Design
- Not defining a protocol (to be written)
- Naming your application components after akka concepts
- Too many actor systems
- Blindly ignoring dead letters (to be written)
Afraid you may have anti-patterns in your application?
Maybe the Reactive Audit is something for you.