HashiCorp Consul — Service Discovery & Service Mesh

What it is

Consul is a distributed service networking platform by HashiCorp. It provides service discovery, health checking, key-value storage, and a full service mesh with mutual TLS (mTLS) for microservices. Consul works across data centers and cloud providers, making it a core piece of infrastructure for distributed systems.

It serves platform engineers, DevOps teams, and backend developers who manage microservice architectures and need automated service registration, health monitoring, and secure inter-service communication.

How it saves time or tokens

Consul automates service registration and discovery, eliminating manual configuration of service endpoints. Health checks remove unhealthy instances from the service registry automatically, reducing incident response time. The built-in service mesh handles mTLS certificate rotation and traffic policies without requiring application code changes.

How to use

1. Deploy Consul agents on each node in your infrastructure (server mode for the cluster, client mode for application nodes).
2. Register services using configuration files, HTTP API, or service mesh sidecar proxies.
3. Query the DNS interface or HTTP API to discover healthy service instances and route traffic.

Example

# consul-service.hcl - Register a web service
service {
  name = 'web-api'
  port = 8080

  check {
    http     = 'http://localhost:8080/health'
    interval = '10s'
    timeout  = '2s'
  }

  connect {
    sidecar_service {}
  }
}

# Start Consul agent and register service
consul agent -dev -config-file=consul-service.hcl

# Query for healthy instances
consul catalog services
dig @127.0.0.1 -p 8600 web-api.service.consul

Related on TokRepo

• AI Tools for DevOps — Infrastructure and deployment automation tools
• AI Tools for Monitoring — Service monitoring and observability solutions

Common pitfalls

• Running too few server nodes. Consul requires a quorum (3 or 5 servers recommended) for fault tolerance.
• Misconfiguring health check intervals so aggressively that flapping services cause cascading failures.
• Ignoring ACL configuration in production, leaving the cluster open to unauthorized service registration.