We asked users how they are using HashiCorp Consul, here’s what they told us.
Last month, we asked users what they do with HashiCorp Consul for their personal deployments or at work. We collected a variety of responses demonstrating that Consul provides solutions for all types of use cases. In this post, we’ll explore some of the setups and insights our users shared.
With that in mind, I want to give a huge thank you to everyone who participated in our survey — we hope these stories highlight solutions that can help new users get up to speed faster. So, without further ado, let’s explore the stories you shared! Starting of course with…
Unsurprisingly for us, many users are taking advantage of Consul’s robust service mesh capabilities. A number of survey respondents said they are using a Consul service mesh for internal projects or to support their entire infrastructure. Take a look at some of the quotes:
“For our internal project we are using Consul for migration of microservices on Kubernetes. I especially like ... its mesh service, in which it connects all clusters in one go and is an easy task for us to search if anything is down.” - Udbhav
“We used Consul as our service discovery mesh for our microservices and it helped us to manage incoming traffic to the product.” - Ashish Kumar Das
“Unifying Kubernetes services and virtual machines services in the same catalog, mesh datacenters, service discovery. We also use the KV store as a [HashiCorp] Vault backend, Saltstack pillars, and specific tools! Can't wait for 1.10 GA, Consul is the heart of our infrastructure, never down in 5 years!!!” - Alexandre Le Mao
“We are using Consul mainly as Vault storage. Secondary use cases are service discovery and connecting two clusters together using mesh gateways for testing Consul Connect capabilities as service mesh.” - Robert Vojcik
“I use it for simple and secure application delivery.” - Anonymous
This exciting mix of uses for Consul service mesh reinforces something that we’ve seen from lots of users: The foundation of a service mesh traditionally starts with solving the service-discovery challenge. Fortunately, Consul is a trusted service discovery tool capable of discovering applications running in any environment.
Aside from Consul’s KV store, the majority of responses focused on Consul’s capabilities as a service discovery and health monitoring tool. The path to Consul’s automation capabilities (service mesh or network infrastructure automation) are made possible by utilizing Consul as a centralized source of truth for application information. Don’t take our word for it though, here’s what survey respondents had to say:
“We run an e-learning platform on ERPNext on Kubernetes. Each custom app is a service and Consul manages the service discovery. We also use [the] Consul key value store for storing configuration.” - Anonymous
“In production. Used for its DNS control between services, and for a quick status check for our services.” - Jonathan Yu
“Service discovery/traffic shaper (no Connect, just making sure traffic only goes to healthy apps)” - Jessy St. Pierre
“Service discovery across apps running directly on [Amazon] EC2, in [Amazon] ECS and on Kubernetes. Some configuration distribution (live updating configuration with KV waits). Storage backend for Vault. Connect on Kubernetes-deployed apps” - Anonymous
“We are using Consul for its service discovery features and the KV. With both features, we have a fully featured CMDB always up to date. We manage to bind Ansible/AWX inventory to Consul as well, which allows us to deploy [a] targeted playbook on the correct set of servers.” - Anonymous
We also asked users which technologies they were using alongside Consul — and we got some great responses. Here is a word cloud representing the technologies cited by our users:
Two key things emerge from this list:
These are capabilities that we’ve prioritized in Consul, and it’s great to see users implementing these features into their environments.
Another common thread across survey responses was Consul’s ability to integrate with other HashiCorp tools. In the word cloud above, HashiCorp Terraform, Nomad, and Vault are all featured prominently. Many users mentioned that they are integrating Consul with Vault and Nomad for various uses.
Consul was originally the primary backend for Vault and it remains a popular option among the survey respondents. In addition, Consul’s Vault integrations extend much deeper. To learn more, check out our collection of HashiCorp Learn guides for integrating Vault and Consul.
From a Terraform and Nomad perspective, the use cases are straightforward, but still impactful. The Consul Terraform provider makes it easy to deploy a Consul service mesh alongside your infrastructure and Consul-Terraform-Sync (CTS) helps automate Day 2 operations for networking infrastructure. To learn more about installing and getting started with CTS, take a look at these Learn guides.
Leveraging Consul with Nomad is a great approach for users who are managing containers or a mixture of containers and non-containerized applications and want to use Consul’s discovery or mesh capabilities to accelerate their application delivery lifecycle. Check out this Learn guide to see how to secure Nomad jobs with Consul service mesh.
It was a joy to learn about the many ways users are connecting with Consul and we again want to thank everyone who participated in the survey. For more information about Consul, please visit the documentation.
Here’s how to keep track of your Apache Camel services running throughout a deployment, and enable them to communicate with one another in a multi-cloud or hybrid cloud environment.
Consul 1.10 can transparently intercept and redirect traffic to sidecar proxies in the service mesh to allow applications to be deployed without modification.
HashiConf Europe speakers from Starbucks and Roblox share how they leverage HashiCorp Vault, Consul, and Boundary to create a zero trust security model.