Introducing Akka Cloud to Edge Continuum. Build once for the Cloud. Seamlessly deploy to the Edge - Read Blog

Fireside Chat: How Akka Works - Reliable Message Delivery In Reactive Systems

An Akka Expert's Answers To Non-Expert Questions

Watch on YouTube

If you've got a free hour, why not sit down and relax with our Developer Advocate, Hugh McKee, and me while we talk about how Akka works. These conversations are designed to provide some knowledge about Akka for beginners and advanced users alike. That's why I'm here, to ask questions on behalf of the beginners about the basics of Akka, and get to understand WHY things have been designed to do what they do in Akka. At the same time, Hugh is able to venture into the intricacies and new features of this cloud native toolkit.

In this discussion, we focus mainly on how message delivery works between actors, nodes, and clusters, including a new feature in the latest release of Akka called Reliable Delivery. I ask Hugh to give us a breakdown of how messaging works in distributed systems vs traditional monolithic architectures, and how things start to get trickier as you distribute your actors across different JVMs, Kubernetes pods, clusters and datacenters.

We believe that you can get a better viewing experience by watching the video above, so you can see our faces and gestures as we delve into this topic. However, if not convenient, we have an audio-only version below on SoundCloud. We hope you enjoy it!

Audio Only Version

Listen on Soundcloud

More Akka Resources

We've got some additional educational content that you might enjoy. Now that Lightbend Academy is open to all until June 30, 2020, there are several courses on Reactive Architecture, Akka Cluster, Akka Streams and more. Here are some other places to learn about Akka:

Or, if you'd like to set up a demo or speak to someone about using Akka in your organization, click below to get started in that direction:



The Total Economic Impact™
Of Lightbend Akka

  • 139% ROI
  • 50% to 75% faster time-to-market
  • 20x increase in developer throughput
  • <6 months Akka pays for itself