But now, there's one thing that I'm not too happy about: both distributed pubsub and distributed data seem to replicate all data onto all nodes instead of spreading out to the cluster. That's not true – pubsub only sends data to such nodes, which subscribed to a given topic.
If all people are in all chat rooms, then yes it will be sent to all nodes. But is that really the case? Some people are in `apples chat room` and you can co-locate them, others are on `oranges chat room` and you can co-locate them, decreasing the amount of traffic and network hits a lot. With a distributed map it's a bit weird to do such things. And this was the reason why I was thinking of Hazelcast. What would a pure akka implementation of this be? Exactly what you explained and I don't see a problem with it. "Let's add a distributed map" does the same thing - all nodes see the updates, so what would the upside be? Downsides in terms of increasing complexity I've explained. Note: I don't mean to say bad things about Hazlecast here – in this scenario we're talking about though I don't see the need for it, but I see a lot of mental and complexity cost associated with introducing it. Hope this helps! -- Konrad -- >>>>>>>>>> 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.
