Service Meshes: Istio, Linkerd - or No Mesh at All?
summary
Compares Istio (Envoy-based) and Linkerd (own proxy) with concrete tradeoffs: Envoy proxy brings many features and customization, Linkerd prioritizes simplicity and performance; control plane plus sidecar proxies add CPU/memory and latency (Istio cites ~3 ms) and more YAML (example: ~10 lines in Linkerd vs ~30 in Istio for a traffic split). Shows Kiali, Prometheus/Grafana/Jaeger integration, features like routing, canary/mirroring, retries/circuit‑breaking, chaos injection, and mTLS; contrasts using libraries (resilience4j) or stripped-down mesh vs full mesh.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:25What is a service mesh? What problems does it try to solve?
- 5:46Service mesh implementations
- 10:42Service mesh features
- 22:22Service mesh challenges
- 26:05Do You need a service mesh?
- 29:02Conclusion
- 32:21Outro
related talks
34mService Mess to Service Mesh
35mNavigating the Service Mesh Ecosystem
52mService Mess to Service Mesh
44mService Mesh - The New Single Point of Failure
30mService Mesh Is Still Hard. The Things we all Did Wrong & Tales of Woe
43mWTF Do We Need a Service Mesh?
40mComparison of Current Service Mesh Architectures
34mService Mesh for Developers
