Hi, I'm trying to choose the best pattern to implement cluster wide distribution of massages/work with ordered processing requirements - of course with all attitudes of Akka location, transparency, fault tolerance and so on.
In fact I'm going to migrate previous implementation based on extended version of disruptor pattern which looks like this <https://lh3.googleusercontent.com/-gkdePmRMDYI/U5b3qnR6plI/AAAAAAAAick/lxTTI3lLZYk/s1600/disruptor-multi-ring.jpg> I see two potential implementation pattern which I could use - Singleton actor with work distribution similar to one presented in this article (http://letitcrash.com/post/29044669086/balancing-workload-across-nodes-with-akka-2) - Extension of the routing logic, something similar to akka.routing.ConsistentHashingRoutingLogic Second option would be more natural and flexible, but I'm not sure if the cluster wide configuration of the router will work ? Does anyone know if this particular commit introduce this type functionality ? (+con #3669 Possibility to define routing logic in DistributedPubSub - https://github.com/akka/akka/pull/1778) or I'm mixing different stuff ? Diagram of the design two design strategies below <https://lh5.googleusercontent.com/-FQfKxp3n4Ms/U5b5oaxFfOI/AAAAAAAAic0/Sj0rpCAiX_I/s1600/akka-topic.png> many thanks in advance I guarantee good blog post about this topic ;) Marek Prochera -- >>>>>>>>>> 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.
