Article - Microservice architectures using ProtoActor

[rogeralsing]

From chat:

I would say there are two common approaches to services using Proto.Actor.
One approach is to have a cluster for a specific micro service, or rather for a sub-system.
where that sub-system lives on its own. say a telemetry processor for IoT. where actors are used for the parts inside that sub-system only.
This sub-system could ofcourse interact with other systems, using any standard mechanisms, say http/grpc/queues etc.

Another approach is to use a cluster for all your services, as Proto.Actor clustering is basically built around service discovery. meaning you could have some nodes hosting service A, and some other nodes hosting service B etc. and they can all know about eachother due to the service discovery.
Both works very well. I personally tend to favor the sub-system approach as it helps keep things more isolated

But you are right, all of this needs to be documented and explained more in detail