Hi, We are working on implementing common services backbone using Akka. To start with, we are implementing a service registry mechanism and evaluating Distributed Data for implementing it. I was going through ServiceRegistry samples at https://github.com/akka/akka-samples/blob/master/akka-sample-distributed-data-scala/src/main/scala/sample/distributeddata/ServiceRegistry.scala and was curious to know if there is any specific reason to maintain local state for list of services in ServiceRegistry actor.
In our implementation, we are directly sending Get message to Replicator while doing service lookup. Is there is any downside of sending Get message directly to Replicator? I am interested in knowing if Distributed Data for Service Locator is used in any of the projects you know of, and to know any lessons learnt. Just curious, is this something that is used internally by ConductR as well? Thanks, Unmesh -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
