Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala.
Why Akka? Documentation
50 million msg/sec on a single machine. Small memory footprint; ~2.5 million actors per GB of heap.
Asynchronous and Distributed by Design. High-level abstractions like Actors, Streams and Futures.
Write systems that self-heal.
Adaptive cluster management, load balancing, routing, partitioning and sharding.
Asynchronouos non-blocking stream processing with backpressure.
Organizations with extreme requirements rely on Akka and other Lightbend technologies. Read about their experiences in our case studies and learn more about how Lightbend can contribute to success with its commercial offerings.
See our news and articles for more good reads
May
19
2017
In previous post we learned about supervision and how to restart a behavior in case of failures. Related to that is the actor’s lifecycle and how to watch an actor...
May
16
2017
Supervision semantics in Akka Typed have changed slightly compared to supervision in classic untyped actors. Untyped actors are by default restarted when an exception is thrown. The default for typed...
May
12
2017
Message protocols are an essential part of designing actor based systems. The interaction between actors are often stateful and messages are supposed to be sent in a certain order, e.g....
May
08
2017
In the introduction blog post we introduced the APIs Actor.mutable and Actor.immutable. We recommend the immutable style as the “default choice” and now we will illustrate the two styles with...
