3 ms·
The use case for actors is any time you want to distribute work across multiple nodes. In general, actors are a great concurrency model that simplifies a lot of
by unoti 6y ago
The use case for actors is any time you want to distribute work across multiple nodes. In general, actors are a great concurrency model that simplifies a lot of the complexity of distributed programming.
For more info on "why", see:
https://doc.akka.io/docs/akka/current/typed/guide/actors-intro.html https://doc.akka.io/docs/akka/current/typed/guide/actors-int...
https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/Orleans-MSR-TR-2014-41.pdf https://www.microsoft.com/en-us/research/wp-content/uploads/...
- tartoran 6y agoThanks, the first link answers some of my questions. >Use of actors allows us to: > Enforce encapsulation without resorting to locks. > Use the model of cooperative entities reacting to signals, changing state, and sending signals to each other to drive the whole application forward. > Stop worrying about an executing mechanism which is a mismatch to our world view. Did anyone here use Goblins for any project and would like to share their experience?
- snicker7 6y agoThe author posted some interesting applications using Goblins (a video game and chat app). There is some interest in porting Goblins to Guile Scheme to integrate with GNU Shepherd (a service orchestrator) ... somehow.
- blandflakes 6y agoI don't want to distract from this comment, because I think it's spot on, but I think another interesting use for actors is as one of the few sane concurrency models for mutation. Pony does this - objects are actors by default. Things can act concurrently without fear external to an object, but all mutations within a given object are serialized. Seems like a nice set of defaults.