From 619b5c97c106f4fd757be853ae82b2c3b665ce53 Mon Sep 17 00:00:00 2001 From: Alexander Brandstedt Date: Fri, 24 Mar 2017 12:30:09 +0100 Subject: [PATCH 1/2] Change service discovery example to use consul/etcd --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0cf09dd..cc32fca 100644 --- a/README.md +++ b/README.md @@ -729,7 +729,10 @@ Pinterest, for example, could have the following microservices: user profile, fo ### Service Discovery -Systems such as [Zookeeper](http://www.slideshare.net/sauravhaloi/introduction-to-apache-zookeeper) can help services find each other by keeping track of registered names, addresses, ports, etc. +Systems such as [Consul](https://www.consul.io/docs/index.html) and [Etcd](https://coreos.com/etcd/docs/latest) are among the newer commonly used pull based service discovery solutions today. They solve service registration/de registration of what name, address and port the service is available at. Health checks are often done using a http endpoint. Both Consul and Etcd also have a built in key/value store that can be useful for storing config values or other shared key/values for running a service + +Systems such as [Zookeeper](http://www.slideshare.net/sauravhaloi/introduction-to-apache-zookeeper) is a possible older system that can be used as a service discovery service. Zookeeper has commonly been used for master election since it isn't a AP + ### Disadvantage(s): application layer From ea461bf23a07f3f5a601fd36ddb63c7160d56661 Mon Sep 17 00:00:00 2001 From: Donne Martin Date: Sun, 26 Mar 2017 12:50:23 -0400 Subject: [PATCH 2/2] Polish service discovery changes --- README.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/README.md b/README.md index cc32fca..bb19f04 100644 --- a/README.md +++ b/README.md @@ -729,10 +729,7 @@ Pinterest, for example, could have the following microservices: user profile, fo ### Service Discovery -Systems such as [Consul](https://www.consul.io/docs/index.html) and [Etcd](https://coreos.com/etcd/docs/latest) are among the newer commonly used pull based service discovery solutions today. They solve service registration/de registration of what name, address and port the service is available at. Health checks are often done using a http endpoint. Both Consul and Etcd also have a built in key/value store that can be useful for storing config values or other shared key/values for running a service - -Systems such as [Zookeeper](http://www.slideshare.net/sauravhaloi/introduction-to-apache-zookeeper) is a possible older system that can be used as a service discovery service. Zookeeper has commonly been used for master election since it isn't a AP - +Systems such as [Consul](https://www.consul.io/docs/index.html), [Etcd](https://coreos.com/etcd/docs/latest), and [Zookeeper](http://www.slideshare.net/sauravhaloi/introduction-to-apache-zookeeper) can help services find each other by keeping track of registered names, addresses, and ports. [Health checks](https://www.consul.io/intro/getting-started/checks.html) help verify service integrity and are often done using an [HTTP](#hypertext-transfer-protocol-http) endpoint. Both Consul and Etcd have a built in [key-value store](#key-value-store) that can be useful for storing config values and other shared data. ### Disadvantage(s): application layer