Re: [akka-user] Suggestions for cluster wide recipient list

2017-01-11 Thread Ivan Nakov
Hi Patrik, The main problem with Distributed Pub/Sub is that in order to kick-off the process I must load all of my persistent actors on startup to be able to subscribe them :). There is also a passivation on the actors. If they are not updated for a long time I want to shut them down but don't

Re: [akka-user] Suggestions for cluster wide recipient list

2017-01-11 Thread Patrik Nordwall
You can perhaps use Distributed Pub/Sub for this. The difficult part is to reliably deliver the messages to all subscribers. Messages may be lost or subscribers may not be running when you consume the message from Rabbit. That is not

[akka-user] Suggestions for cluster wide recipient list

2017-01-11 Thread Ivan Nakov
Hi guys, I have a service that consumes messages through RabbitMq channel and should forward them to PersistentActors behind ClusterShard. The tricky part is that each persistent actor must subscribe himself for a specific messages and receive all messages from these types. For example: message