We’ve been looking at this as a core part of microservices-infrastructure [1],
so I have been thinking of this problem a lot.
We’re using consul [2] as our service discovery engine. We like the fact that
it already has an http api, WAN dns discovery, and health checks at the agent
level.
Ok, this is a bit long, I apologize in advance
I’ve been researching and experimenting with various challenges around managing
microservices at-scale. I’ve been working extensively with Docker, CoreOS and
recently Mesos.
First, I think that we need to clearly distinguish that service
Hi Yaron,
(Also apologies for the long reply)
First, I think that we need to clearly distinguish that service
discovery, and request routing / load balancing are related but separate
concerns. In my mind, at least, discovery is about finding a way to
communicate with a service (much like a DNS
This discussion reminds me of a few excellent blog posts on solving similar
problems.
Smart clients vs dumb load balancers:
http://blog.lusis.org/blog/2013/05/13/smart-clients/
Then there is the local haproxy idea, which I think is a lot less
applicable to a mesos environment, but still worth
John,
I will throw in my 2 cents:
There are a number of open-sourced offerings done by well known companies in
this area and I have tried a few of them. Generally my opinion is that they
are a little restrictive.
We are using the HAProxy service on each slave as you described. We have
I figured I would comment on how Banno is setting up service discovery with
mesos. We've built everything around docker containers and then a wrapper
around that which we call sidecar that handles service discovery, basic
process supervision, and hot reloads of the underlying app config.
: Current State of Service Discovery
I figured I would comment on how Banno is setting up service discovery
with mesos. We've built everything around docker containers and then a
wrapper around that which we call sidecar that handles service discovery,
basic process supervision, and hot reloads
That approach sounds similar to Smartstack
(http://nerds.airbnb.com/smartstack-service-discovery-cloud/).
From: Adam Shannon [mailto:adam.shan...@banno.com]
Sent: Wednesday, April 01, 2015 10:58 AM
To: mesos-users
Subject: Re: Current State of Service Discovery
I figured I would comment on how
Kesler dkes...@yodle.com wrote:
That approach sounds similar to Smartstack (
http://nerds.airbnb.com/smartstack-service-discovery-cloud/).
*From:* Adam Shannon [mailto:adam.shan...@banno.com]
*Sent:* Wednesday, April 01, 2015 10:58 AM
*To:* mesos-users
*Subject:* Re: Current State of Service
On 04/01/2015 11:20 AM, Christos Kozyrakis wrote:
Service discovery is a topic where it's unlikely that a single solution
will satisfy every need and every constraint. It's also good for the
Mesos community to have multiple successful alternatives, even when they
overlap in some ways.
I will
10 matches
Mail list logo
