Hi Eugene,
You could have the creation of actor A (and subsequently the B actors) done by
a master actor that represents a service inside the cluster, and the response
you get from that master contains a named topic or something similar where the
FSM can communicate with the A actor.
Have you
Hi, Björn!
Thanks for the response.
The biggest problem is that the original system was developed without any
clustering in mind - so on every request from the client, a new FSM actor
is created, some pre-defined references to worker actors are passed to the
FSM actor and then it orchestrates
Hello!
I have an FSM actor. which takes a number of references to worker actors
in it's constructor. That works very well if there's a single actor system.
Now I want to create another worker actor *in the cluster* and get a
reference to this actor in the FSM actor *outside of the cluster*, so