Just what is a "service mesh", and if I get one will it make everything OK?
summary
Defines a service mesh by showing Istio deployed on Kubernetes (docker desktop single-node) with an example app split into ~13 services and three review backends, and demonstrates real features: Envoy proxy injected per pod, routing rules that send canary 20% of traffic to a new version, fault injection adding a 5s delay, and mutual TLS with short-lived certificates (auto-rotated ~3 months). Demos include Pilot/Citadel/Mixer, Jaeger traces, Prometheus/Grafana metrics — everything runs and the controls apply at runtime.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:30WHAT IS A SERVICE MESH?
- 7:53INTRODUCING ISTIO
- 13:49YOUR SERVICE MESH IS NOT FREE
- 27:49TRAFFIC MANAGEMENT
- 55:30SERVICE MESH ALTERNATIVES
- 56:56DO I NEED A SERVICE MESH?
- 58:49THINK ABOUT THE COST
related talks
10mWhat the heck is a Service Mesh ?
43mWTF Do We Need a Service Mesh?
28mService Mesh: Demystifying Istio
46mWhat the hell is service mesh anyway !?
26mAn Introduction to Service Mesh in Action
39mDo you need a Service Mesh?
53mDo you need a Service Mesh?
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...