For a mission-critical system such as payment processing for a bank, you need complete assurance that the system is fault-tolerant and can gracefully handle periods of unavailability, network SNAFUs, and other associated software fun and games.

This presentation makes a powerful case for a combination of two Akka concepts - clustering and distributed data - to demonstrate how you can persist state across the cluster and therefore not need to worry about individual nodes going down for maintenance, or indeed for unforeseen reasons. We also deal with the fact that we might need to only be able to run one instance of an actor in a cluster, by introducing the concept of a cluster singleton.

We then go on to write a simple TFTP server in Akka, which runs in an Akka cluster and uses Akka Distributed Data to distribute client data. So any member of the cluster that receives a request for data is able to handle it independently.

YOU MAY ALSO LIKE:

• Fast Track to Android Architecture (in London on 21st - 23rd October 2019)
• Real World Kotlin Development Workshop (in London on 22nd - 23rd October 2019)
• Scala eXchange London 2019 (in London on 12th - 13th December 2019)
• London Java Community July (in London on 24th July 2019)
• Keynote by Adam Bien on Productivity with Micro Frontends and Cloud-native Backends (in London on 15th August 2019)
• Write Now, Run Anytime (SkillsCast recorded in June 2019)
• Java in the Age of Containers and Serverless (SkillsCast recorded in June 2019)