we—the Akka committers—are proud to be able to announce the availability of Akka 2.5.0-RC1 (FIRST RELEASE CANDIDATE). Since the release of Akka 2.4.0 (already 18 months ago) we have incrementally added many new features to the 2.4.x release series, including Akka Streams and HTTP. That has worked well and we think you appreciate the API stability of all those patch versions. As always, there are some changes one cannot do in patch versions and therefore it is time for Akka 2.5. One of these changes is to promote some of the experimental modules to fully stable modules and incorporate some API improvements before declaring them stable.
The key features of the 2.5.0-RC1 release are:
- The Java API for AbstractActor was promoted to fully stable API. While doing this we made some small, yet important, improvements to the API that will require some mechanical changes of your source code.Thanks to @ortigali for help.
- Faster and more flexible Akka Streams materializer, which matters for short lived streams, such as HTTP requests.
- Distributed Data was promoted to a fully stable module. Several improvements were also included, such as:
- Coordinated shutdown to facilitate ordered stopping of actors and services and perform registered tasks during the shutdown process. This greatly simplifies tasks involved in graceful leaving of Akka Cluster.
- Support remembering entities in Cluster Sharding with the Distributed Data (ddata) mode. ddata is now also the default mode for Cluster Sharding.
- New Java API for Testkit taking advantage of lambas, thanks to @Hawstein
- Fix performance regression for Scala 2.12, due to change in scheduling fairness of the JDK8 ForkJoinPool implementation
- We added @ApiMayChange and other annotations which can be used to mark experimental API inside stable modules, primarily for use in Akka HTTP. API improvements of Akka Typed, including Java API
Akka 2.5.x is backwards binary compatible with previous 2.4.x versions (exceptions listed below). This means that the new JARs are a drop-in replacement for the old one (but not the other way around) as long as your build does not enable the inliner (Scala-only restriction). It should be noted that Scala 2.12.x is is not binary compatible with Scala 2.11.x, which means that Akka’s binary compatibility property only holds between versions that were built for a given Scala version — akka-actor_2.12-2.5.0-RC1.jar is compatible with akka-actor_2.12-2.4.17.jar but not with akka-actor_2.11-2.4.17.jar.
Binary compatibility is not maintained for the following:
- akka-testkit and akka-multi-node-testkit
- modules and API marked as “may change”, such as akka-typed and akka-contrib
- features, classes, methods that were deprecated in 2.4.0 or earlier and removed in 2.5.x
We had to make two additional exceptions:
- Custom Mailbox implementations. Scala 2.12 is using the standard JDK8 ForkJoinPool, which may cause performance regression for some Actor messaging scenarios. Therefore we have embedded the ForkJoinPool from Scala 2.11 in Akka. This breaks binary backwards compatibility for custom Mailbox implementations that were compiled with Akka 2.4.
- To make the Java APIs
AbstractPersistentActorWithAtLeastOnceDeliveryto work with Scala 2.12 we could find no other solution but to break the binary compatibility of the Scala versions (which the Java ones were based on).
Being binary backwards compatible means that applications and libraries built on top of Akka 2.4.x continue to work with Akka 2.5.x without recompilation (subject to the conditions below), which implies that Akka HTTP as well as Play Framework 2.5 can be combined with Akka 2.5.
When migrating a code base to Akka 2.5 please refer to the migration guide in order to profit from some of the improvements.
AbstractActor has been promoted from its experimental state and while doing this we did some small, but important, improvements to the API that will require some mechanical changes of your source code. See the Actor (Java) section in the migration guide.
It is possible to do a rolling update from Akka 2.4.17 to 2.5-M1 but some configuration changes might be needed first. See the Rolling Update section in the migration guide.
Akka Persistence plugins released for 2.4 might not be compatible with the changes that were done in the API for Persistence Query in 2.5. We kindly ask the Akka Persistence plugin maintainers to migrate and release for 2.5. See the Persistence Query section in the migration guide. Akka Persistence plugin for Cassandra with version 0.50-RC1 that is compatible with Akka 2.5.0-RC1 has been released.
Akka 2.3 is End-of-Life
Akka 2.3.0 was released 3 years ago and with the release of 2.5.0 it will be officially declared as end-of-life, which means that we will not backport bug fixes and make new releases. If you are still using Akka 2.3 it’s highly recommended that you update. Use the migration guide for 2.4 and then the migration guide for 2.5.
For this release (since 2.5-M2) we had the help of 29 contributors – thank you all very much!
Credits: commits added removed 30 8474 763 Patrik Nordwall 25 15182 2833 Johan Andrén 12 389 227 Konrad `ktoso` Malawski 11 5065 3429 drewhk 10 321 122 Johannes Rudolph 6 602 319 Martynas Mickevičius 4 100 148 ortigali 3 37 44 sebastian.harko 2 472 79 Björn Antonsson 2 152 31 Josep Prat 2 146 35 Richard Imaoka 2 42 37 Aurélien Thieriot 1 4310 79 gosubpl 1 1817 762 Roland Kuhn 1 1091 563 Hawstein 1 558 27 Maciej Ciołek 1 339 10 cchantep 1 275 20 Qingwei 1 89 1 Daniel Urban 1 46 12 Kirill Yankov 1 52 1 Michał Płachta 1 7 7 Nafer Sanabria 1 13 1 Sergey 1 6 0 A Andrievsky 1 2 2 Tal Pressman 1 2 2 bill 1 2 0 toaditoad 1 1 1 Devis Lucato 1 1 0 haggy
– The Akka Team