Catalogue / doordash-2024-service-mesh-zone-routing

DoorDash cuts AWS cross-AZ transfer and ELB spend with Envoy EDS zone-aware routing, soft pod spreading, and co-locating Iguazu

DoorDash, 2024. Cell-based microservice traffic infrastructure and Envoy service mesh.

Organisation
DoorDash
Evidence
Reported from production
Source
Staying in the Zone: How DoorDash used a service mesh to manage data transfer, reducing hops and cloud spend

DoorDash Engineering, published 2024-01-16

Records

Decision#d1

Enable Envoy zone-aware routing via EDS and soft Kubernetes pod spreading across availability zones

Decision#d2

Attribute remaining cross-AZ transfer spend by combining VPC flow logs, Envoy byte metrics, and node eBPF metrics

Decision#d3

Move Iguazu into client cells and reroute client Envoy sidecars directly to pods, bypassing its ELB

Sign in to read what was chosen, what was rejected and what it cost, each with its place in the source. An account is free.