How to get a grip on your microservices system using a service-mesh
summary
Demoed a small “pit stop” garage app running on Docker Desktop Kubernetes with Istio+Envoy, Prometheus, Grafana, Kiali and Jaeger; sidecars use automatic injection and metrics appear without app changes. Deploys V2 behind a service with mirror 100% to V2 then shifts traffic with a 25% canary and later 50/50, allowing zero‑downtime cutover. Chaos scenarios inject faults — inject 25% HTTP 500 faults — and built‑in Polly retries prove resiliency; observability dashboards show traces, errors and traffic distribution.
AI-written summary · about
chapters (9)
- 0:00Introduction to service mesh
- 1:40The service mesh concept
- 4:56How service mesh works
- 9:26Istio implementation details
- 14:28Demo application overview
- 20:07Observability with Istio
- 28:21Traffic routing and releases
- 43:20Resiliency and chaos testing
- 49:35Final thoughts and advice
related talks
51mHow to get a grip on your microservices system using a service mesh
52mEmpower Your Microservices with Istio Service Mesh
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
01h 01mIstio Service Mesh & pragmatic microservices architecture
55mEmpower Your Microservices with Istio Service Mesh
34mIstio, We Have a Problem! Understanding and Fixing Bugs with a Service-Mesh
52mMaking microservices micro with Istio Service Mesh & Kubernetes
50mService Mesh and Sidecars with Istio and Envoy