I see that Akka has it's own routing implementation based on a consistent hashing function. Many of the popular Memcached clients typically uses a Ketama hash to do their version of this.
We have a use case where we want to route messages based on the server in which their co-located data would be in Memcached. Is the best approach here to write our own router hashing implementation that uses a Ketama hash similar to our Memcached client? Another option it seems would be to airlift Akka's consistent hashing function for deciding where to write. -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
