Consul

There are numeric options for service registry and discovery in Light; however, Consul is the most important one as almost all our customers are using it. For development purpose, you can use Docker to start a single instance Consul server. The command line can be found in the discovery tutorial.

For production, the deployment is more complicated. If you have multiple data centers, you’d better use the enterprise edition and let HashiCorp install it. For simple cloud deployment, you can follow the consul tutorial to install a three nodes cluster. When using Light, there is no need to install the agent to the service host. A three nodes cluster of Consul server would be enough to support hundreds or thousands of service instances.

Consul Registry Checklist

When you are using Consul for service registry and discovery, the following configuration updates need to be done to connect to the consul cluster. client.truststore and client.keystore The Consul certificate needs to be imported into the client.truststore. client.yml If the consul cluster doesn’t have a domain name, you need to set the verifyHostname to false consul.yml update the consulUrl and other parameters. User httpCheck if possible. Read More »

Cluster Install

Introduction HashiCorp Consul provides distributed, highly available, datacenter-aware service registry and discovery for microservices. It allows services to register itself and client to discover interested services. In the following tutorial, we are going to install a three nodes Consul cluster in three KVM VMs. It is recommended that you have 3 or 5 Consul servers running in each data center and each instance should be installed in a physical machine or a VM. Read More »