Delivery Done Right with Service Mesh
summary
Shipt replaces per-cluster hairpin DNS with a single global hostname per service and stitches 60+ clusters and ~400 services into a multi-cluster mesh using Istio + Envoy and Solo’s Glue to get multi-cluster mTLS and automatic failover. The platform runs ~3K RPS, deploys via GitOps (Helm, Concourse), and centralizes a regional ingress gateway with WAF/OIDC and Vault-backed PKI so cross-cluster identity and retries short‑circuit extra hops for lower latency and stronger policy enforcement.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:39Technology at Shipt
- 2:15Grass Roots Service Mesh
- 3:42Scaling Service Mesh Expertise
- 5:50Start Early
- 6:44Why Service Mesh?
- 8:09Choosing Service Mesh
- 8:44Existing Architecture
- 11:08Mesh Architecture
- 11:47Mesh Integrated Gateway
- 12:58Tiered Gateway
- 14:31Shipt Routing pre Service Mesh
- 15:24Multi Cluster DNS
- 16:33Multi Cluster No Mesh
- 19:42Proxy DNS
- 24:41Conclusion
related talks
24mMulticluster Service Mesh
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
43mService Mesh and the future of networking
45mIstio Service Mesh Simplified Beyond a Single Cluster
11mWelcome & Opening Remarks
34mService Mesh for Developers
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
43mWTF Do We Need a Service Mesh?
