This document discusses the actor model and how to design systems to fail gracefully. It introduces actors and the core concepts of the actor model including messages, mailboxes, and supervision. It then covers various techniques for mitigating failures like exponential backoff, circuit breakers, and throttling. The document also discusses patterns for distributed systems using actors like load balancing, consistent hashing, and virtual actors.
1 of 38
Download to read offline
More Related Content
Failing Gracefully with the actor model
1. Failing gracefully
With the actor model
Roger Johansson
Akka.NET and Proto.Actor Founder
Solution Architect - Betsson Group
Twitter: @rogeralsing
Github: rogeralsing
Mail: rogeralsing@gmail.com
Github.com/rogeralsing/presentations
http://Proto.Actor
3. An escalator can never break: it can only become stairs.
You should never see an Escalator Temporarily Out Of Order
sign, just Escalator Temporarily Stairs.
Sorry for the convenience.
-Mitch Hedberg
6. Actor Model
Three axioms:
Send an actor can send messages to other actors
Create an actor can create new actors
Become an actor can decide how to handle its next message
7. An island of consistency in a sea of concurrency
Shared nothing, Black box
Location transparent, Distributable by design
Actor Model
36. Node A
433
Node B
24345
Node C
82327
Hash:
989123
Node E
943772
Node D
612344
Node F
987234
Grain Id:
Roger
Names:
Roger
Names:
Roger
Actors:
Roger : User
Virtual Actors
38. The End
Roger Johansson
Twitter: @rogeralsing
Github: rogeralsing
Mail: rogeralsing@gmail.com
Github.com/rogeralsing/presentations
http://Proto.Actor