WTF Do We Need a Service Mesh?
summary
Service mesh is a sidecar+control-plane pattern that makes service-to-service networking manageable by adding proxies (Envoy, Linkerd2 proxy) and control APIs (SMI). It enables traffic split, progressive delivery (blue/green, canary) and observability (service-level percentiles, success/failure counts); Istio drops from ~50 to ~20 components since 1.0, is available as a managed GKE add-on, and suffers mixer hot spots addressed by mixer v2/WASM. Benchmarks claim Linkerd (Rust proxy) outperforms Istio; alternatives include Consul, Traefik/Kuma approaches and Network Service Mesh for L2/L3 use cases.
AI-written summary · about
chapters (11)
- 0:00Start
- 9:03QUESTIONS
- 12:35MESH VS GATEWAY
- 14:27SMI - THE SERVICE MESH INTERFACE
- 26:08LINKERD 2.0
- 27:54CONSUL CONNECT
- 31:13KUMA (KONG MESH)
- 32:21NSX - NETWORK SERVICE MESH
- 34:08ECOSYSTEM!
- 37:10BENCHMARKS
- 40:43GET INTO THE MESH
related talks
10mWhat the heck is a 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
11mWelcome & Opening Remarks
34mService Mesh for Developers
35mNavigating the Service Mesh Ecosystem
46mWhat the hell is service mesh anyway !?
33mService Meshes: Istio, Linkerd - or No Mesh at All?
