If one actor carries very important data (i.e. its state shall not be lost if avoidable), this actor should source out any possibly dangerous sub-tasks to children it supervises and handle failures of these children as appropriate. Depending on the nature of the requests, it may be best to create a new child for each request, which simplifies state management for collecting the replies. This is known as the “Error Kernel Pattern” from Erlang.
Questions tagged [error-kernel]
4 questions
8
votes
2 answers
Handling Faults in Akka actors
I've a very simple example where I've an Actor (SimpleActor) that perform a periodic task by sending a message to itself. The message is scheduled in the constructor for the actor. In the normal case (i.e., without faults) everything works fine.…
Soumya Simanta
- 11,523
- 24
- 106
- 161
1
vote
1 answer
Akka supervisor strategy for different types of actors
I'm using Akka and I want to define my own supervision strategy for User Guardian actor. I've defined two types of actors, called TaskActor and MessageActor. They're instantiated as top-level actors.
I wish the user guardian to apply the following…
Mattia Micomonaco
- 230
- 1
- 12
1
vote
2 answers
Error kernel and supervision in Akka: will messages from stale children be delivered to restarted actor?
I am trying to follow best practices and apply error kernel pattern in Akka. According to this quote from here:
If one actor carries very important data (i.e. its state shall not be lost if avoidable), this actor should source out any possibly…
Eugene Loy
- 12,224
- 8
- 53
- 79
0
votes
1 answer
Where and how to use actors in practice
How could actors be used in complex back-end services, that are made of receiving an initial request, doing some processing, then sending some requests/things-to-do to other services, waiting for responses from some of them, and deciding how to…
rapt
- 11,810
- 35
- 103
- 145