Case Study: Criteo achieves lower-latency, scalable service mesh infrastructure with HashiCorp Consul Connect

How Criteo went from Physical Hosts/DCs to Containers with Consul and Connect

Criteo, a global ad retargeting company, needed a way to move from a large bare-metal, multi-datacenter environment to containers without sacrificing the low latency and scale its business depends on. With more than 22,000 nodes, high request volumes, and many services across Windows and Linux, Criteo was struggling with the complexity and cost of traditional load balancing and custom client-side load balancing code.

HashiCorp helped Criteo use Consul and Consul Connect to provide service discovery, secure service-to-service communication, and a path toward service mesh architecture across mixed workloads. The approach reduced reliance on dedicated load balancers, improved flexibility across languages and platforms, and supported a transition to containers; in testing, Consul Connect showed lower latency than load balancer-based routing and enabled coverage across about 450 services and 10,000 instances.

Criteo

Pierre Souchay

Discovery and Security Authorization Lead