Estimate project
← All posts

Your Akka has reached End Of Life – what now?

Since October 2023, Akka 2.6.x is past its end of life. Which steps should you take next?

3 min read
JavaScalaAkkaArchitectureMigration

In September 2022 Lightbend caught the Scala community off guard with the news that every future Akka release would switch from the Apache 2.0 license to the “source available” Business Source License (BSL) v1.1. In practice, companies with more than US $25 million in annual revenue that want to use the newer versions must purchase a Lightbend commercial subscription.

Akka End Of Life

The 2.6.x branch is the final Akka line under the Apache license. The change was announced following the 2.6.20 release, but later on, in June 2023, Akka 2.6.x received a critical fix and version 2.6.21 came out. As of October 19, 2023, Akka 2.6.x has officially reached its end of life and won’t get any more critical security updates.

Keep in mind too that Akka 2.6.x works with Scala 3 thanks to CrossVersion.for3Use2_13, although complete native Scala 3 support isn’t offered. Officially, Akka 2.6.x supports JDK 11, but workarounds exist that make it run fully on JDK 17.

If Akka 2.6.x is still part of your stack, now is the moment to think about your next move!

Lightbend commercial license

One possibility is to keep using Lightbend releases and, once revenue exceeds $25 million, buy a commercial license. This path comes with both benefits and drawbacks. Certainly, no one enjoys paying for licenses. Still, there are some upsides. New Akka releases are built under the SOC 2 standard. They offer full JDK 17 and Scala 3.3 support as well as new functionality like Akka Edge or Akka Distributed Cluster with Projections over GRPC, enabling communication between Microservers without a broker. Should you require 24/7 support, this could also be the right choice.

Lightbend ended FY24 with record growth and gained 50 new customers.

Apache Pekko

Apache Pekko is a fork of Akka 2.6.x driven by the community. It is being incubated by the Apache Foundation under the Apache license 2.0. Pekko 1.0 adds support for Scala 3 LTS and JDK 17 (and, judging by GitHub, it has already been tested on JDK 21). The upcoming 1.0.3 release is set to make rolling upgrades from Akka to Pekko possible. Notably, projects like Alpakka have also been moved into the Pekko Connectors module. Several smaller open source projects state that they are compatible with Akka 2.6.x and support Pekko, or intend to add such support. Support for the newer commercial Akka releases is something you’ll see in them rather rarely.

To learn more about Pekko and its modules, check the project’s documentation, as well as its GitHub repository containing the source code.

Migrate away?

A license change in a major library is also a good opportunity to pause and reflect on where the project is heading. Is Akka still the right choice? How has it served your project over the past years? Did you run into any problems? Some teams choose to move to other technologies, and some even go as far as rewriting in another programming language. Much also depends on which particular Akka libraries are in use – a plain Akka HTTP setup is certainly simpler to replace than a full-scale solution built on Akka Cluster with Akka Persistence.

Conclusions

Choosing what to do about EOL Akka 2.6.x in your project isn’t straightforward. Many factors come into play, such as your team’s skills, hiring plans, and past experience. If you rely on Play Framework, these issues may affect you too.

At our company, we’ve worked on a variety of systems built on Akka and Play. Right now we’re helping our clients figure out the best next steps for their projects. For some, Pekko is the best choice; for others, the Lightbend subscription may be; and for still others, moving to a different, simpler tech stack. Our goal is to give the best recommendation for each customer’s particular situation.