Over the past decade, Akka has pioneered the field of Reactive Systems–systems that are elastic, resilient and message-driven so as to be at all times responsive to the users, no matter what. Companies like Disney+, Starbucks, and PayPal depend on these architectural principles to go hand-in-hand with those of cloud native application infrastructure like Kubernetes, which emphasize automation, resilience, and scalability in highly dynamic cloud-based environments.
While the classic Akka APIs have been used for building the foundation of many mission-critical systems across industries, they also contain shortcomings, or anti-patterns, that made building these systems challenging for new users. If you’ve ever worked with Akka Actors in the past, you may have experienced sending a message to an actor that doesn’t exist, for example. Well, no more.
With the release of Akka 2.6, however, this sort of mistake and many other shortcomings of the Classic Actor APIs have now been rendered impossible by design, allowing new users to more easily embrace Akka’s actor model. In this special guest webinar with Manuel Bernhardt, Akka expert and Reactive System Consultant, we go over:
If you're already an Akka user, or want to learn more about adopting this game-changing toolkit for distributed, cloud-native applications, why not schedule a demo with us to see what Akka looks like in production as part of a Lightbend subscription. You'll get to see features for observability, telemetry, and system health monitoring, as well as Akka resilience and persistence enhancements only available to subscribers, like Akka Split Brain Resolver and Akka Multi-Datacenter support.
