It is hard to explain, but in short my master actor receives a message
which is then forwarded to the respective worker, and from that message I
extract business information to make my worker's (FSM) persistenceId
unique.
After I second thought, maybe I misunderstood the router concept - I jus
What persistenceIds would you like to use in the end?
Based on a counter? PO-1, PO-2, ... increasing for each routee?
Would be strange in a long running system when worker nodes are added and
removed over time.
Why not use Cluster Sharding instead? Wouldn't it be more natural to have a
separate e
To explain my issue in a clear way I provided a sample code:
if I have an actor which looks like this:
class MasterActor extends Actor with ActorLogging with WorkerRouter with
AkkaProvider {
private val router = createWorkerRouter()
def receive = {
case PurchaseOrderMsg(content,
