Service Meshes - Powering the next wave of microservice architectures
summary
Service meshes move retries, circuit breakers, mutual TLS and routing out of app code into Envoy sidecars and a control plane like Pilot/Mixer/Citadel (Istio) running on Kubernetes. Demos show 50/50 and percent-based canary swaps, traffic mirroring of live traffic to an unpublished version, outlier detection that ejects instances after five errors for 20s, and retries of up to three attempts with a 2s timeout (vs 15s default). Start with observability, add policies gradually.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 29:42Service mesh architecture
- 31:17Testing in production
- 32:32Traffic mirroring demo
- 34:12Canary releases
- 35:43Circuit breakers
- 37:27Chaos engineering
- 40:30Observability and tools
- 41:52Advanced traffic management
- 44:21Final thoughts
- 45:24Q&A session
related talks
34mService Mesh for Developers
43mService Mesh and the future of networking
53mService Mesh: What, Why, And How?
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
01h 01mIstio Service Mesh & pragmatic microservices architecture
11mWelcome & Opening Remarks
55mEmpower Your Microservices with Istio Service Mesh
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
