Service mesh options with Istio, Linkerd, and/or Consul
summary
Service mesh implements per-call Envoy sidecars as a data plane with a separate control plane to deliver secure communication, resilience and telemetry. Demo uses Istio (Citadel, Mixer), Linkerd (Rust proxy, always-on mTLS in recent release), Consul Connect (identity-first, no L7 yet) and AWS App Mesh (managed control plane, Envoy proxies). Superglue automates installs and can register meshes; a Shopify comparison shows Linkerd uses less CPU by default but Istio outperforms when Mixer is removed.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:00Mean Time to Recovery
- 5:24Fallacies of Distributed Computing
- 6:57Service Discovery
- 12:35Envoy
- 19:53Linker D
- 21:34Always-On Mutual Tls
- 22:14Linker D Strengths
- 24:15Console Service Registry
- 29:36Aws App Mesh
- 37:11Install Sto
- 42:38How Do You Ensure a Control Plane Does Not Become Your Single Point of Failure and if It's Scaled How Do
- 45:59Do You Think It's Worth Using Service Mesh over a Simple Api Gateway Model
related talks
26mNavigating the Service Mesh Landscape - Paul Bouwer, Microsoft
43mService Mesh and the future of networking
26mChoosing a Service Mesh
38mPanel Discussion: Ask Us Anything: Microservices and Service Mesh
44mService Mess to Service Mesh
53mService mesh across hybrid infrastructure
34mContainer Networking Untangling Services Meshes and SDNs
31mClean-up Your Service Mess with Service Mesh