Hello, Igor. Try Consul https://www.consul.io/ It's well documented, well tested (using Jepsen) and has a lot of useful features beside service discovery e.g. monitoring, distributed locking, KV-storage, etc.
On Wed, 13 Jan 2016 00:14:44 -0800 (PST) Igor Katz <[email protected]> wrote: > > > Hi, > > > We need a service registry where all our components will turn to for > discovering the actual URLs which they can use to communicate to > other parts of our system. The service has to provide a load > balancing and fault tolerance. It has to be distributed to prevent > production outage. In CAP > <http://codahale.com/you-cant-sacrifice-partition-tolerance/> terms, > it has to be AP. > > > Thanks, > > Igor > > On Wednesday, January 13, 2016 at 1:45:00 AM UTC+2, Michael Frank > wrote: > > > > On 01/12/16 07:28, Igor Katz wrote: > > > > Hi, > > > > We are going to use Akka-HTTP as IPC in our new distributed system > > that is based on microservice architecture. How to perform Service > > discovery for akka-stream/akka-http in distributed system? What is > > the best way to implement this? > > > > what are your requirements? > > > > -Michael > > > -- Best regards, Eax Melanhovich http://eax.me/ -- >>>>>>>>>> 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.
