Service Mess to Service Mesh
summary
Live demos with Istio and Linkerd show concrete tradeoffs: Linkerd installs in minutes and focuses on a fast, self-contained getting started while Istio offers built-in telemetry and advanced routing that enables 80/20 traffic split A/B tests and user‑targeted rollouts. Both provide mutual tls via a control plane that issues certificates, but adding a mesh roughly doubles sidecar count and commonly raises cluster overhead to about 1.5x resource usage. The choice is operational cost versus bundled features and control.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:12Traffic metaphor
- 3:35Service Mesh
- 11:33Service Mesh Examples
- 20:28Intelligent Routing
- 23:43QA
- 24:47Kafka
- 25:37Graphql
- 26:11Kali Console
- 27:07Prometheus Dashboard
- 28:00Proxying
- 28:46Using a Service Mesh
- 29:43Why Use a Service Mesh
related talks
52mService Mess to Service Mesh
33mService Meshes: Istio, Linkerd - or No Mesh at All?
27mService Mess to Service Mesh
35mNavigating the Service Mesh Ecosystem
30mService Mesh Is Still Hard. The Things we all Did Wrong & Tales of Woe
45mService Mesh War Stories - Lessons Learned the Hard Way
43mWTF Do We Need a Service Mesh?
20mThe Crazy Service Mesh Ecosystem
