An Introduction to Service Mesh in Action
summary
Shows an Istio-based service mesh wiring Envoy sidecar proxies into Kubernetes and using Kiali + Grafana + tracing for observability, with a concrete performance gap of 20 seconds vs 3–5 ms between user profile v2 and v1. Demonstrates fixing by changing virtual service routing, deploying v3 and shifting 10% canary then 50/50, and a circuit breaker that ejects failing pods so traffic returns to the healthy version. Adds mutual TLS and a request authentication policy so unauthenticated curl calls fail, proving the controls actually work.
AI-written summary · about
chapters (13)
- 0:00Service mesh intro
- 1:28Why service mesh matters
- 3:58Microservices challenges
- 6:42How service mesh solves
- 8:48Service mesh architecture
- 11:14Observability with Kiali
- 13:40Metrics and tracing
- 15:48Fixing with dynamic routing
- 18:17Canary deployments
- 20:41Circuit breaking
- 22:48Security with mutual TLS
- 24:35Authentication and authorization
- 25:16Resources and closing
related talks
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
34mService Mess to Service Mesh
28mService Mesh: Demystifying Istio
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
52mEmpower Your Microservices with Istio Service Mesh
34mService Mesh for Developers
01h 01mIstio Service Mesh & pragmatic microservices architecture
52mService Mess to Service Mesh