Vanishing Point: Reimagining the Meaning of a Mesh
summary
Ambient mesh replaces per-pod sidecars with a per-node zTunnel L4 proxy (Rust) plus on-demand Envoy waypoint pods for L7, cutting CPU/memory and operational surface by eliminating thousands of sidecars; upgrades happen without app restarts and only long TCP streams see transient disruption. Work is underway to push L4/identity into the CNI integration and to let cloud providers supply managed load balancers as waypoint replacements, with multicluster ambient slated for early alpha development.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:28Service mesh in 2019
- 3:57Redefining service mesh
- 8:09Service mesh evolution
- 13:26Ambient mesh benefits
- 16:37Consistent APIs in infrastructure
- 18:43Service mesh as APIs
- 20:28Future vision
- 20:50Q&A: Ambient mode
- 22:20Q&A: Z-tunnel upgrade
- 23:02Q&A: Ambient in Kubernetes
- 24:27Closing
related talks
24mArchitecting Ambient Mesh for Scale
05mOptimize Sidecarless Service Mesh With A Brand-New Rust-Base...
26mBeyond Wasm: How Dynamic Modules Let You Extend Envoy Proxy in Go, Rust, or…
52mEnable all your infrastructure’s power with Rust & Wasm
22m"Low-Overhead Observability in High-RPS Servers"
17mProxyless gRPC Service Mesh for Rust
05mInterview
29mRust: Embedded, Async, All the Way