Service Mesh use cases for Telco and Edge
summary
Positions service mesh as the control plane for telco/5G/edge deployments, claiming concrete gains: Google uses Traffic Director plus envoy sidecars and a proxyless gRPC mode to support mixed VM/container workloads, enable traffic mirroring, fault injection, mTLS and cross-region overflow/failover. Shows a working warehouse video-intelligence stack on Google edge infrastructure. Cites 25 billion devices by 2025, Gartner’s 75% edge processing prediction, and notes only ~5% of enterprise apps are containerized today, driving the need for compute-agnostic meshes.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:20Key industry trends
- 2:18Drivers for Edge
- 3:14Where is the Edge
- 4:37How enterprises can use Edge
- 5:52Customer Edge example
- 7:31Telco 5G
- 10:28Challenges
- 14:40Benefits of Service Mesh
- 15:13Service Mesh Benefits
- 15:45Service Mesh Definition
- 16:56Service Mesh implementations
- 17:34Service Mesh example
- 18:08Traffic control
- 18:45Fault injection
- 20:11Endtoend visibility
- 21:19VMbased services to container services
- 22:30Legacy appliances and clients
- 24:49Cross cluster cross region failover
- 26:16Core telco network
- 26:30Service based architecture
- 26:45Service mesh control plane
- 27:50Extensibility
- 28:47Service Mesh innovations
- 29:32Un effortless edge problem
- 31:55Un effortless network slicing problem
- 33:32Summary
related talks
43mService Mesh and the future of networking
18mHigh Performance Service Meshes with gRPC Proxyless
30mTo Mesh or not to Mesh
05mKeynote: Service Mesh Everywhere
47mService-Mesh: an In-Depth View of Technologies and Reasons for Adoption
47mService mesh options with Istio, Linkerd, and/or Consul
41mPanel Discussion: Service Mesh Maturity: Are We There Yet?
31mThe Future of Service Meshes: Sidecarless or eBPF?