This document discusses designing systems to fail gracefully using the actor model. It introduces concepts like actors, the actor model, and implementations in different languages. It then covers techniques for mitigating failures like exponential backoff, circuit breakers, throttling, bounded mailboxes, limiting concurrency, and work pulling. Finally, it discusses virtual actors which can distribute work across nodes to ensure work is never lost.
1 of 40
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
40. The End
Roger Johansson
Twitter: @rogeralsing
Github: rogeralsing
Mail: rogeralsing@gmail.com
Github.com/rogeralsing/presentations
http://Proto.Actor