Hi, we are building a message processing system, which is basically looks like a classic chat room:
~ 1 million devices are connected via websockets to a dozen of nodes - each of them subscribes on a number of topics - each of them publishes updates to the topics, and we should deliver these updates to subscribed devices The problem is, a number of topics is huge, like x100 times more than a number of devices. Right now we are using Redis to store device-to-subscription and device-to-node relations. On each topic update, we are looking in cache to find all devices to notify and node addresses, where these devices are connected at the moment. We are not using Akka Cluster yet, but looks like it's Pub/Sub functionality perfectly matches with our case and we can get rid of our logic and cache. *The only question, is it capable to manage tens of millions of topics? Would it perform better then our current solution?* -- >>>>>>>>>> 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.
