Service Mess to Service Mesh
summary
Explains how a sidecar proxy + control plane enforces mTLS and policy so services get observe control secure behavior without code changes, with live demos of linkerd (smooth install, linkerd check, linkerd viz, Grafana) and istio (istioctl, Kiali, Jaeger). Shows canary/AB routing (33/33/33 split, 20% traffic to v2), beta routing by logged-in user to v3, circuit breaker behavior, and warns of extra runtime cost (roughly 1.3–1.6x CPU or near doubling container count).
AI-written summary · about
chapters (6)
- 0:00Start
- 5:25Microservices
- 6:22Api Gateway
- 10:34Circuit Breakers
- 14:35Grafana Dashboard
- 23:05Kiali Dashboard
related talks
34mService Mess to Service Mesh
30mService Mesh Is Still Hard. The Things we all Did Wrong & Tales of Woe
50mService Mesh and Sidecars with Istio and Envoy
35mNavigating the Service Mesh Ecosystem
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
38mAsk Me Anything About Service Mesh
33mMircoservices the right way: an introduction to Istio
43mWTF Do We Need a Service Mesh?
