Blog Posts

One anti-pattern I’ve observed in networked Akka applications is a tendency to forget that it is, well, networked and to treat the network as a friendly place. How does that look like? Well, consider the following piece of code: [crayon-597a16abe8702729450439/] Akka’s default message sending mechanism is the fire-and-forget tell method. And that works great – until it doesn’t. See, tell ... Read More

The post Akka anti-patterns: trusting the network appeared first on manuel bernhardt.

Whilst I have always successfully discouraged my clients from using Akka Remoting in their application, I often get questions regarding remoting while talking about anti-patterns at conferences and user groups. Don’t get me wrong. I love Akka remoting. Especially the new Aeron-based Artery remoting version that is based on UDP rather than TCP. Whilst it maintains the same delivery guarantees, ... Read More

The post Akka anti-patterns: using remoting appeared first on manuel bernhardt.

Akka anti-patterns: blocking
15.05.2017 07:59 by Manuel

This is probably one of the most frequent (and dangerous) anti-patterns when it comes to working with Akka. Let’s look at an adequate description of the mindset you must be in in order to use it: So maybe you didn’t actually want to see the world burn. Maybe you thought that this one time it was okay to call blocking ... Read More

The post Akka anti-patterns: blocking appeared first on manuel bernhardt.

Choosing Akka as a tool is often – if not always – driven by the need for good performance. Surely, the actor model itself is appealing as a means for organizing and reasoning about code, but this isn’t in itself a good reason enough to use the Akka toolkit. If all you are concerned about is a nice way to ... Read More

The post Akka anti-patterns: being out of touch with the hardware appeared first on manuel bernhardt.