Polish service discovery changes

pull/36/head
Donne Martin 2017-03-26 12:50:23 -04:00
parent 619b5c97c1
commit ea461bf23a
1 changed files with 1 additions and 4 deletions

View File

@ -729,10 +729,7 @@ Pinterest, for example, could have the following microservices: user profile, fo
### Service Discovery ### 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 [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.
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 ### Disadvantage(s): application layer