Consul Use Cases At Stripe: Service Mesh and More
summary
Stripe describes a Consul-backed multi-region service networking stack that runs 30 Consul clusters and supports tens of thousands of agents across domains and regions, federated with WAN federation plus pairwise network areas. Envoy serves as the proxy with an internal control plane compiling Consul catalog into consistent xDS configs; Kubernetes pods register via host agents and UDS proxies. They report ongoing issues with gossip traffic limits, use snapshots to S3 for recovery, and enable network segments and redundancy zones to scale and improve availability.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:24Stripe service networking
- 5:37Consul deployment topology
- 7:21Service mesh evolution
- 11:13Consul with Kubernetes
- 13:22Consul challenges
- 16:33Consul availability
- 19:00Consul scalability
- 20:46Future plans
related talks
40mIntroducing A New Architecture for Simplified Service Mesh Deployments
22mA Hands-on Approach to Consul Deployment Strategies in a Hybrid Environment
19mService Mesh and Your Legacy Apps: Connecting to Kubernetes with Consul
24mDeployment Patterns for Consul in Kubernetes
54mUsing Terraform and Consul to delegate service deployment to service teams
43mConsul Learn Lab: Deploy Resilient Applications with Service Mesh and AWS Lambda
44mDecoding the Service Mesh landscape
26mNavigating the Service Mesh Landscape - Paul Bouwer, Microsoft