Akka.NET is a toolkit and runtime for building highly concurrent, distributed, and fault tolerant event-driven applications on .NET & Mono.
This community-driven port brings C# & F# developers the capabilities of the original Akka framework in Java/Scala.
Learn about Akka for the JVM here.
Asynchronous and Distributed by design. High-level abstractions like Actors and FSM.
50 million msg/sec on a single machine. Small memory footprint; ~2.5 million actors per GB of heap.
Write systems that self-heal. Remote and/or local supervisor hierarchies.
Adaptive load balancing, routing, partitioning and configuration-driven remoting.
Use Akka.NET Extensions to adapt Akka to fit your needs.
Akka.NET is released under the Apache 2 license
The Actor Model provides a higher level of abstraction for writing concurrent and distributed systems. It alleviates the developer from having to deal with explicit locking and thread management, making it easier to write correct concurrent and parallel systems.
Actors were defined in the 1973 paper by Carl Hewitt but have been popularized by the Erlang language, and used for example at Ericsson with great success to build highly concurrent and reliable telecom systems.
Everything in Akka.NET is designed to work in a distributed setting: all interactions of actors use purely message passing and everything is asynchronous.
This effort has been undertaken to ensure that all functions are available equally when running within a single process or on a cluster of hundreds of machines. The key for enabling this is to go from remote to local by way of optimization instead of trying to go from local to remote by way of generalization. See this classic paper for a detailed discussion on why the second approach is bound to fail.
Actors form a tree with actors being parents to the actors they've created.
As a parent, the actor is responsible for handling its children’s failures (so-called supervision), forming a chain of responsibility, all the way to the top. When an actor crashes, its parent can either restart or stop it, or escalate the failure up the hierarchy of actors. This enables a clean set of semantics for managing failures in a concurrent, distributed system and allows for writing highly fault-tolerant systems that self-heal.