The actor-based paradigm is pretty steep. Its ability to scale effectively makes it a paradigm that needs to be evaluated for any parallel system. I have read something about this, and I have a decent idea of the main intentions: manage your expensive operation with messages and several "actors" to minimize expectations due to interaction with the request / response, thereby increasing the throughput of your system. However, I did not have enough impact on the design patterns that people use with actors. I am looking for design patterns for acting systems.
A common example of an actor’s design pattern is a system in which there is an actor-master coordinator and a group of child labor participants. They cope with an expensive operation into smaller pieces, send smaller pieces in the form of messages to a handful of workers, wait for answers from them, and then reduce them all to the result. In some complex examples of this template, participating workers notify the wizard that they are ready for more work, and the master routes to them work more on demand. This provides the right balance of work and is useful when job sizes change quite a bit.
I was looking for literature on more actor-based patterns and could not find any examples other than the above. I have yet to go through Akka Actors project projects, but any pointers would be very helpful.
source share