Service Mesh: What, Why, And How?
summary
Claims that a service mesh provides application‑level resilience, observability, and security, and then shows it working: an Envoy sidecar mesh managed by Istio with an Ambassador API gateway on Kubernetes. Demo changes routing from reviews v1 to v2 via Ambassador config, deletes the reviews v1 deployment and traffic continues, and an external auth mapping returns 401 for /qtm/quote until credentials are provided. Also covers circuit breakers, rate limits, metrics aggregation and Envoy sidecar Istio control plane Ambassador gateway.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:53What is a Service Mesh
- 3:40Jane
- 4:50Felicia
- 6:35Julia
- 7:06Can it always help
- 7:23What does it mean to deploy
- 9:55What does it mean to worry about
- 21:48Trusting the individual
- 22:44Envoy
- 29:55The Point of the Service Mesh
- 30:52Things that cannot do that
- 32:04Using API Gateways
- 33:27Conclusion
- 34:23Questions
- 34:49Blackbird
- 35:22Kubernetes
- 36:12Pods
- 42:20Web Browser Demo
- 43:24Typing While Looking
- 44:01HTTP
- 44:58Podlist
- 45:11Reviews
- 45:51Kubernetes idiom
- 46:26Force a redeployment
- 47:26Deleting kubernetes
- 48:59External authentication service
- 50:07Fana
- 50:26Quote
related talks
28mService Mesh: Demystifying Istio
28mService Mesh and Sidecars with Istio and Envoy
34mService Mess to Service Mesh
47mService Mesh and Sidecars with Istio and Envoy
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
45mSolving Microservice Problems with Service Mesh: Istio and Envoy
50mService Mesh and Sidecars with Istio and Envoy
56mService Meshes - Powering the next wave of microservice architectures