Actors as in Actor Model? #86
Description
Im curious as to the design of the actors library and concepts you are using. When I saw actors, I was expecting an actor model implementation. Is that the intent?
If so, is it based on prior work? I found surprising the inclusion of a few points, e.g. RPC, and lack of others, e.g. message queue for input.
A few more questions to which I didn’t see answers (apologies if I missed them):
- How are concurrent requests managed?
- Since the API appears to be synchronous, are there any guarantees about ordering of requests?
- How do they handle backpressure?
- Are these concerns left to the developer or handled within the platform?
Either way, thank you for your work on this library!