Panel: Ask Me Anything: Microservices and Service Mesh [B]
summary
Panel summarizes practical tradeoffs and deployments: Istio as a pluggable control plane with Envoy/Linkerd data planes, large-scale reality is Envoy on ~20k hosts handling ~5M requests/sec, proxies typically add ~1ms per hop, Linkerd reports p99s around 5ms. Sidecar injection requires a rolling redeploy so no app code changes (but need rolling restart), though tracing needs a tiny library to propagate span IDs. Main payoff is unified observability and pluggable control/data APIs, not magic zero-cost performance.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:33Panel Introductions
- 2:40What is Service Mesh
- 10:00Control Plane Data Plane
- 12:45Envoy Enhancements
- 14:28Envoy Filters
- 15:59Service Mesh Challenges
- 22:41Service Mesh and Networking
- 25:04Networking Libraries
- 31:50DevOps
- 33:53Wrapup
related talks
37mPanel Discussion: Ask Us Anything: Microservices and Service Mesh
38mAsk Me Anything About Service Mesh
35mNavigating the Service Mesh Ecosystem
49mMaking Microservices Micro with Istio Service Mesh
33mService Meshes: Istio, Linkerd - or No Mesh at All?
45mService Mesh War Stories - Lessons Learned the Hard Way
27mService Mess to Service Mesh
46mPanel: Ask Me Anything About Istio Service Mesh