Service Discovery in Docker Using NGINX and NGINX Plus with Consul

In a microservices application, the set of running service instances change dynamically and their assigned network locations keep changing as well. Consequently, in order to load balance requests across the most recent set of service instances, a load balancer like NGINX must use a service-discovery mechanism.

NGINX, Inc.'s commercial offering, NGINX Plus, further improves service discovery integration by enabling you to dynamically add or remove servers in a load-balanced group as they are discovered via Consul, using either NGINX Plus' HTTP-based API or by re-resolving DNS records through Consul's DNS interface. This also eliminates the need to reload the NGINX Plus configuration every time there is a change the set of load-balanced servers.

[diegoramos]

Does NGINX use a Registrator for the Registration ? or each client must register itself ? thanks

[jarredobrien]

Can NGINX update any of its documentation regarding NGINX Plus and service discovery? These topics are woefully out of date.