As of a few moments ago, we released Akka.NET 1.1 - the biggest feature release we’ve done for Akka.NET since releasing 1.0 last year! We have other major Akka.NET feature releases planned for later this year, but this is the first and one of the most long-awaited ones.
Akka.Cluster is released from beta
The biggest change in this release is the first stable release of Akka.Cluster, which has been in various beta stages since August 2014. During that time it’s been used as a beta package by hundreds of users who have given the Akka.NET project large amounts of bug reports and feedback.
Since that time we’ve covered Akka.Cluster in a huge range of multi-node tests, designed to ensure the cluster behaves correctly under a variety of network conditions (including some rather hostile ones) and it’s performed well.
We’ve also replaced the underlying Helios 1.4.1 transport with a brand new Helios 2.1.1 transport, which delivers up to 5x the throughput with a tremendously lower memory footprint than the previous versions.
Release of the Multi-node TestKit, Multi-node Test Runner
One tool that has proven utterly indispensable in the development of Akka.Cluster, Akka.Remote, Akka.Cluster.Tools, and Akka.Cluster.Sharding is the
Akka.Remote.TestKit package - commonly referred to as the “multi-node testkit.”
This library is an extension of the
Akka.TestKit that developers use for unit testing simple actors, and it offers capabilities designed for facilitating distributed unit tests for Akka.NET
ActorSystems that are using Akka.Remote, Akka.Cluster, or any of the other high availability (HA) modules.
The Akka.Remote.TestKit is designed to allow you to do the to following:
- Run a unit test across multiple processes simultaneously, simulating how servers or virtual machines would behave in the real-world;
- Offers a dead-simple Domain Specific Language (DSL) that allows...