There's never too much of a good thing

Akka anti-patterns: Too many actors

Manuel Bernhardt’s Akka anti-patterns series continues. This time, he takes a closer look at a very frequent anti-pattern that can be found in codebases written by developers who have just discovered the actor model; and that is to have too many actors. Whilst Akka is entirely capable and designed to run many actors, this isn’t always the best approach.

You sure you've been doing it the right way?

Akka anti-patterns: Java serialization

The Akka documentation discourages the use of Java serialization but performance is just one reason to not use Java serialization – there are stronger reasons to not engage with it, especially in the context of Akka. What to do instead? In this article, Manuel Bernhardt gives some alternatives.

Useful or not?

Akka anti-patterns: Stateless actors

What is the importance of actors and why stateless actors make little sense? In this article, Manuel Bernhardt briefly explains the main purpose of actors and their state.

Trivial pursuit

How well do you know your Akka trivia?

It’s time for another programming pub quiz! This week, we’re testing your knowledge about Akka. Do you know everything there is to know about this toolkit for building concurrent applications on the JVM?


A tour of Akka cluster – Cluster sharding

The tour of Akka cluster continues! In the previous article, we learned how to use techniques for making a reactive payment processor resilient to failure using Akka Cluster. Here, Manuel Bernhardt takes a closer look at how to scale out the reactive payment processor application using cluster sharding.

Let's go exploring!

A tour of Akka Cluster – Akka distributed data

How can we make building distributed systems easier? In this article, Manuel Bernhardt explores one useful tool in the Akka toolbox: Akka Cluster. Today, we’re taking a closer look at one module, Akka Distributed Data, and how it can be used to build an example reactive payment processor.

Actors are analogous to Lego or Minecraft blocks

Akka clusters: All about Cluster Aware Actors

The fundamental building block of Akka actor systems is an actor. In a way, actors are analogous to Lego or Minecraft blocks: With the simple building blocks of Lego and Minecraft, it is possible to craft magnificent structures. In this article, Hugh McKee, developer advocate at Lightbend tells you everything you need to know about cluster aware actors.

How Akka is used to create distributed systems or clustered virtual machines

Akka clustering and remoting

While there is a wealth of documentation around Akka, based on Lightbend’s real-world experience with users and customers over the last few years, they realized that there is a need for tutorial-style tips that focuses on different aspects of Akka. In this post, Hugh McKee focuses on Akka clustering vs. Akka remoting.

SMACK — Next generation Big Data

Big Data becomes Fast Data

Big Data is changing. Buzzwords such as Hadoop, Storm, Pig and Hive are not the darlings of the industry anymore —they are being replaced by a powerful duo: Fast Data and SMACK. Such a fast change in such a (relatively) young ecosystem begs the following question: What is wrong with the current approach? What is the difference between Fast and Big Data? And what is SMACK?

Akka anti-patterns: being out of touch with the hardware

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.