Skip to main content

Home/ Arquitectura?/ Group items tagged service-discovery

Rss Feed Group items tagged

Pablo Lalloni

Consul Introduction - 1 views

  •  
    "Consul has multiple components, but as a whole, it is a tool for discovering and configuring services in your infrastructure. It provides several key features: Service Discovery: Clients of Consul can provide a service, such as api or mysql, and other clients can use Consul to discover providers of a given service. Using either DNS or HTTP, applications can easily find the services they depend upon. Health Checking: Consul clients can provide any number of health checks, either associated with a given service ("is the webserver returning 200 OK"), or with the local node ("is memory utilization below 90%"). This information can be used by an operator to monitor cluster health, and it is used by the service discovery components to route traffic away from unhealthy hosts. Key/Value Store: Applications can make use of Consul's hierarchical key/value store for any number of purposes including: dynamic configuration, feature flagging, coordination, leader election, etc. The simple HTTP API makes it easy to use. Multi Datacenter: Consul supports multiple datacenters out of the box. This means users of Consul do not have to worry about building additional layers of abstraction to grow to multiple regions. Consul is designed to be friendly to both the DevOps community and application developers, making it perfect for modern, elastic infrastructures."
munyeco

Service Discovery & Orchestration With Mesos and Consul | My Tech Musings and Stuff I W... - 4 views

  • Joel, we chose consul for a few reasons. First, I wanted a service discovery solution that could work with our legacy architectures as well as any new projects we run on mesos. In addition, I wanted a way to bootstrap the mesos cluster setup/configuration (masters and slaves) such that when they are provisioned, they will be auto-configured using data in consul. Think zk values, quorum, etc. I’ll be working on a solution for this very soon. Lastly, I really like how consul supports health-checks, which we will leverage heavily to ensure that only “healthy” services are actually registered. Like you mentioned, consul is very fast in updating the service info and that is very important as well. Hope that helps, -Phil
Chancha Mazzoni

Automatic Docker Service Announcement with Registrator - 0 views

  •  
    No matter which service discovery system you use, it will not likely know how to register your services for you. Service discovery requires your services to somehow announce themselves to the service directory. This is not as trivial as it sounds. There are many approaches to do this, each with their own pros and cons.
Pablo Lalloni

QubitProducts/bamboo - 1 views

  •  
    "HAProxy auto configuration and auto service discovery for Mesos Marathon"
Pablo Lalloni

Docker Service Discovery Using Etcd and Haproxy - Jason Wilder's Blog - 0 views

  •  
    Eureka.
Pablo Lalloni

progrium/registrator - 1 views

  •  
    "Registrator automatically register/deregisters services for Docker containers based on published ports and metadata from the container environment. Registrator supports pluggable service registries, which currently includes Consul, etcd and SkyDNS 2."
1 - 7 of 7
Showing 20 items per page