How to get a grip on your microservices system using a service mesh
summary
Hands-on demo of a Kubernetes microservices app (PitStop: web + three REST APIs, RabbitMQ, SQL) that adds Istio as a service mesh with Envoy sidecars injected per pod (mutating webhook or kubectl inject). Shows observability via Prometheus, Grafana, Jaeger and Kiali, traffic mirroring for dark release, 10% canary routing, and controlled chaos with 25% fault injection returning HTTP 500. Claims runtime overhead is a few percent and the demos work locally and on AKS.
AI-written summary · about
chapters (9)
- 0:00Introduction to microservices
- 10:08Demo application overview
- 12:57What is a service mesh
- 16:26Service mesh components
- 20:45Observability with Istio
- 29:58Traffic routing and releases
- 41:30Chaos engineering with Istio
- 45:34Production considerations
- 48:46Q&A session
related talks
56mHow to get a grip on your microservices system using a service-mesh
52mEmpower Your Microservices with Istio Service Mesh
55mEmpower Your Microservices with Istio Service Mesh
01h 01mIstio Service Mesh & pragmatic microservices architecture
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
52mMaking microservices micro with Istio Service Mesh & Kubernetes
58mService Mesh and Sidecars with Istio and Envoy
33mMircoservices the right way: an introduction to Istio