Architecting Ambient Mesh for Scale
summary
Istio replaces sidecars with a per-node Z tunnel and per-namespace Waypoint, trading full proxy features for a tiny, purpose-built data plane. Z tunnel is written in Rust, uses a compact, opinionated delta + on‑demand protocol, and measures ~30–60 MB vs contrived 4 GB Envoy dumps in tests; Waypoints are Envoy-based and scoped to a namespace. Tests show scaling to tens of thousands of pods and typical resource savings of ~90–99%; control plane adds incremental-change detection to avoid redundant pushes.
AI-written summary · about
chapters (12)
- 0:00Ambient Mesh scalability intro
- 2:06Scalability challenges in EO
- 3:09EO mesh architecture scale issues
- 5:15Envoy proxy config updates
- 8:04Ambient Mesh architecture overview
- 9:30Scaling Z Tunnel protocols
- 13:03Z Tunnel purpose-built design
- 15:08Waypoints and routing
- 17:16Control plane automation
- 18:22Benchmarking resource savings
- 21:31Future-proofing EO with CNIs
- 23:57Next steps for scalability
related talks
25mVanishing Point: Reimagining the Meaning of a Mesh
05mOptimize Sidecarless Service Mesh With A Brand-New Rust-Base...
52mEnable all your infrastructure’s power with Rust & Wasm
26mBeyond Wasm: How Dynamic Modules Let You Extend Envoy Proxy in Go, Rust, or…
13mLightning Talk: Writing Service Mesh Control Planes in Rust
50mHigh Performance Network Programming in Rust
25mFive Years of Cloud Native Rust.
17mProxyless gRPC Service Mesh for Rust