I’m running an akka-typed cluster (with sharding and persistence) and I need a publish/subscribe mechanism.
Is the untyped distributed publish/subscribe as documented in https://doc.akka.io/docs/akka/2.5/distributed-pub-sub.html still the recommended approach for these scenarios?
Or should I use the receptionist, for instance with a service key representing the topic and using Find to retrieve active listeners then sending them the message? If so, it would be nice to have pre-existing wrappers implementing this particular pub/sub scenario.
Also, does the receptionist work like ActorSelection and are registrations persisted in case of recovery or passivation? It would be important that recovered actors are still present in the listing, otherwise how can they receive new messages?