Case Study: Tide achieves self-service service mesh with HashiCorp Consul

Tide's Self-Service Service Mesh With HCP Consul

Tide, a UK business banking provider with about 350,000 members, 250 engineers, and 120 services, needed a better way to secure and manage service-to-service communication across its ECS-EC2 and ECS-Fargate environment. After running into limits and retrofit challenges with AWS AppMesh — including ingress support, upstream limits, mTLS certificate costs, and flexibility for mixed protocols and multiple ports — Tide turned to HashiCorp and HCP Consul.

HashiCorp helped Tide implement a self-service service mesh with HCP Consul as the control plane, sidecar-based service connectivity, and separately managed intentions for fine-grained access control. Tide rolled out the migration in just six weeks with no downtime and no big-bang cutover, while also making service configuration easier for engineers and improving the path toward secure internal ingress and mTLS across services.

Tide

Jez Halford

Head of Cloud Engineering