Decentralized Routing For a Sharded Application On Service Mesh
summary
Intuit moves shard routing out of a central API gateway into the client Envoy sidecar by calling an external lookup service (plus a distributed cache) from a WASM Envoy HTTP filter that rewrites outbound hosts to the shard DNS. A new routing policy CRD is authored by service owners and Admiral translates it into per-cluster EnvoyFilters; demo routes company IDs in the 7k/8k/9k ranges to the correct shards. TinyGo/WASM limits force an external cache and prebuilt proxy binary, but latency is acceptable after caching and CPU impact is small.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:29Intuit Scale
- 3:57Service Mesh at Intuit
- 5:49What is a sharded application?
- 7:18Sharded Routing - MESH
- 8:17Sharded Routing - Goals
- 9:47Sharded Routing-Existing solutions
- 11:53Sharded Routing - Approach
- 13:29Dynamic Routing in Intuit
- 15:07Challenges
- 17:07Demo Setup
related talks
28mEnvoy at Square
29mThe rise of Layer 7, microservices, and the proxy war...
33mUsing Envoy for data aware traffic routing in Azure Service Fabric
24mMulticluster Service Mesh
43mService Mesh and the future of networking
23mA Simplified Service Mesh With gRPC
39mAPI Gateway to Service Mesh: Navigating a Changing Landscape
53mService Mesh: What, Why, And How?
