On Thursday, July 13, 2017 at 2:56:52 PM UTC+2, Justin du coeur wrote: > > (I should note: I don't use Akka Pub/Sub myself, but I'm wondering whether > Cluster Sharding actually fits your use case well. Depending on the > details, it might.) >
Yep, I guess that's true. With cluster sharding each topic would be managed on a single node. If that node goes down you either lose your subscriptions or you have them persisted in which case another node will pick them up after a while. Each message travels from the node where it is ingested to the node with the topic actor and from there to all the nodes that manage the external connections (like WS). Without any extra work, you will have to deduplicate that traffic or you will internally send each message multiple times for each external connection. If a topic is busy, the single topic actor might become a bottleneck. With PubSub, when a node goes down, all subscriptions that had been managed at that node are gone. Each message is in the worst case broadcasted to the topic actor of each other node and from there locally to the subscribers. Johannes -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
