Service Mesh for Developers
summary
Service mesh externalizes retries, timeouts, mTLS and routing to Envoy sidecar proxies programmed by an istiod control plane, so apps need no library changes. Istio supports canaries via VirtualService/DestinationRule (example: 5% canary routing) and fault injection (example: 0.1% delay of 5s). Proxies add real costs—memory can exceed the application—and a mesh spans regions and clusters (Kubernetes can scale to 15,000-node Kubernetes clusters). Managed options include Anthos Service Mesh; monitoring typically uses Prometheus/Grafana or Datadog.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:19What is a service mesh
- 3:02Monoliths to microservices
- 10:26Service-to-service challenges
- 13:58Service mesh architecture and Istio
- 17:51Service mesh and Kubernetes networking
- 20:18Ingress and egress gateways
- 23:05Traffic management policies
- 25:37Service mesh capabilities
- 27:02Multi-cluster service mesh
- 29:27Adopting a service mesh
- 31:55Monitoring in Kubernetes
- 33:40Q&A
related talks
28mService Mesh: Demystifying Istio
43mService Mesh for developers
56mService Meshes - Powering the next wave of microservice architectures
43mService Mesh and the future of networking
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
10mWhat the heck is a Service Mesh ?
25mIstio for Node Developers
26mAn Introduction to Service Mesh in Action
