Service Mess to Service Mesh
summary
Compares Linkerd’s fast, simple install to Istio’s heavier, feature-rich stack and demos a Linkerd quick install and an Istio demo with virtual services driving canary and A/B routing and Grafana/Prometheus/Jaeger/Kiali dashboards. Explains sidecar proxies + control plane enforcing mutual TLS and replacing Kubernetes Service routing, shows zero‑downtime version swaps, and measures cost: roughly 1.4–1.7x compute overhead with small added latency. Covers ingress/egress gateways, policy enforcement, observability, and when multi‑tenant or PCI/PKI workloads justify adoption.
AI-written summary · about
chapters (22)
- 0:00Introduction to service mesh
- 1:50What is a service mesh
- 3:58From monolith to microservices
- 5:23API gateway limitations
- 7:11How service mesh works
- 9:19Observe, control and secure traffic
- 10:03Advanced service mesh features
- 12:11Service mesh reliability
- 13:36Service mesh dashboards
- 14:17Types of service meshes
- 16:04Linkerd demo setup
- 23:22Istio demo setup
- 25:15Istio traffic routing demo
- 29:55Istio monitoring dashboards
- 37:02Service mesh performance impact
- 40:58When to use a service mesh
- 43:03Multi-tenant workloads
- 44:05End-to-end tracing
- 46:30API gateway vs service mesh
- 47:57Service mesh performance cost
- 48:42Service mesh risks
- 50:30Q&A and closing
related talks
34mService Mess to Service Mesh
34mService Mess to Service Mesh
33mService Meshes: Istio, Linkerd - or No Mesh at All?
01h 10mService Mesh Introduction
26mNavigating the Service Mesh Landscape - Paul Bouwer, Microsoft
26mAn Introduction to Service Mesh in Action
44mDecoding the Service Mesh landscape
35mIntro: Linkerd