Making Microservices Micro with Istio Service Mesh
summary
Istio configures a per-instance proxy (Envoy) as a sidecar to handle service-to-service routing, retries, circuit breaking, fault injection and mutual TLS without changing app code; Pilot pushes policies, Mixer forwards metrics to Prometheus and traces to Zipkin. Demo deploys tiny JDK HTTP services to Kubernetes, applies traffic-splitting and a 100% 503 fault, and shows Prometheus/Zipkin capturing failures and traces. Claimed Envoy performance: ~2 million rps. Envoy sidecar proxy Pilot and Mixer control plane
AI-written summary · about
chapters (29)
- 0:00Introduction
- 2:55Problems with Microservices
- 4:17Kubernetes Registry
- 5:05Kubernetes Control Plan
- 6:01Demo
- 7:14Communication
- 8:17Microservices Architecture
- 9:00Open Source Tools
- 9:59Microcircuit Texture
- 10:42Spring Boot
- 11:16Multiple Stacks
- 12:12Service to Service Communication
- 12:40HTTP Request
- 14:22What does it do
- 15:16What does it mean
- 15:40Crosscutting concerns
- 16:20Proxy Envoy
- 16:57Proxy Load Balancing
- 17:50Proxy Control Plan
- 23:17Proxy Control Plan Demo
- 23:50HTTP Server Demo
- 27:53Worker Demo
- 31:43Check out master
- 40:00Prometheus
- 40:33Prometheus metrics
- 42:00Zipkin metrics
- 43:28Injecting failures
- 45:01Testing the Mesh
- 45:24Mutual TOS
related talks
52mMaking microservices micro with Istio Service Mesh & Kubernetes
55mEmpower Your Microservices with Istio Service Mesh
50mMaking Microservices Micro with Istio & Kubernetes
33mMircoservices the right way: an introduction to Istio
50mDeveloping Microservices with Istio
48mIstio An open platform to connect, manage, and secure microservices
01h 01mIstio Service Mesh & pragmatic microservices architecture
52mEmpower Your Microservices with Istio Service Mesh