Most likely, your job is heavily focused on helping your organization modernize for the digital era. As the days of purely Object-Oriented Programming and related frameworks come to a close, enterprises migrating to distributed, cloud infrastructures are embracing a different approach: the Actor Model. When it comes to distributed computing, the Actor Model is the great-grandparent of it all. Created by Carl Hewitt in 1973, Forrester Research notes, “the Actor model is seeing renewed interest as cloud concurrency challenges grow.” Yet even if you understand the Actor Model and used some of the toolkits for it (e.g. Akka and Erlang), how do you easily explain the concept to your team, colleagues and managers? Where do you start? In this webinar, Hugh McKee, Global Solutions Architect at Lightbend, shows you how Actors behave and interact as humans do when it comes to communicating, and how these similar behavioral patterns provide basic intuition when designing Reactive systems. Actors allow your teams to focus on an application’s business logic rather than on low-level protocols, accelerating time-to-market while keeping your infrastructure costs low. Our goal is twofold: provide you with a comprehensive review of the Actor Model, and give you the resources you need to help others learn why enterprises like Walmart, Intel, Samsung, IBM, Norwegian Cruise Lines and HSBC are committed production users of Akka, the JVM-based toolkit built on the Actor Model. In this webinar, you’ll learn: *Why actor-based systems are one of the foundational technologies for creating microservices architecture (MSA) *How Actors delegate work by creating other Actors in a supervisor-to-worker relationship *How Actors manage requests and scale horizontally in large systems *The difference between traditional systems and actor-based systems *How an Actor system forms clusters when the flow of work exceeds a system’s capacity to process it *Why failure detection and failure recovery is an architectural feature of Actor systems *An example of using Actors to build an Internet of Things (IoT) application Visit Lightbend.com/blog for more goodness.

1. WEBINAR
Distributed Systems Done Right:
Why Java Enterprises Are Embracing The Actor Model
Hugh McKee (@mckeeh3), Global Solutions Architect

3. Time to Value

4. Accelerated Time to Value

5. Actors, Humans, and How We Live

6. Actor messages are like text messages

7. Actors behave like humans exchanging text messages

8. No response to your text, what do you do?

9. No response to a text, send another text

10. Still no response

11. Actor A sends a message to B and
later gets the expected response

12. Actor B never responds to message from A

13. Actor A sends message to B and it
responds before the timeout

14. No response from Actor B and A gets timeout message

15. Supervisor actor creates worker actors

16. Worker actor has problem and notifies its supervisor

17. Supervisor fixes worker that has experienced a problem

18. Supervisor actor delegates tasks to worker actors

19. Worker actors perform tasks asynchronously

20. Ten 100 ms tasks performed synchronously take 1 second
asynchronously take about 100 ms to complete

21. Actors and Scaling Large Systems

22. The supervisor add or sheds workers as the
load increases and decreases

23. An office example where workers sit at desks to perform
tasks only when the desk has power

24. One desk has power, so the worker at that desk may
work on its assigned task

25. Messages are sent to the office and then
routed to each worker

26. The system swaps the power between desks to allow an
even distribution of work

27. Backlog forms when messages arrive faster than the
workers can perform each task

28. In an asynchronous system, workers only occupy desks
when they have something to do

29. Actor systems may run in a cluster

30. Actor Failure Detection,
Recovery,
and Self-Healing

31. Actors form hierarchies

32. Actors form hierarchies

33. Actors form hierarchies

34. When a node fails, the sentinel actors are notified via an
actor terminated message

35. Circuit breakers can be used to stop the flow of messages
to an actor when something unusual happens

36. Actors in an IoT Application

37. Device message routing across the cluster using the
consistent hashing algorithm

38. Routing device messages across the cluster using DMRs

39. Addendum: Messaging & RPC

40. Messageing HTTP RPC
HTTP ReST

47. or Asynchronous operation – does it really matter?
Is this a Synchronous operation …

48. In summary…

49. The four tenets of reactive systems

51. Upgrade your grey matter
Get Hugh’s free O’Reilly book from Lightbend
http://bit.ly/actormodel-OR

52. Build modern systems for the modern world
www.lightbend.com