Choosing a Service Mesh
Talkat Linkerd Day Europe 2025 · on Tuesday, 2025-04-01· at 14:10· Level 3 | ICC Capital Suite 14-16·
summary
Compare the Market evaluates Linkerd versus Istio, Kuma and AWS App Mesh using measured baselines for latency and requests per second, strict checks for mutual TLS enforced, and cost modeling of sidecar CPU memory across replicas and clusters. Initial preference for Istio flips after factoring operational load, training time, runbooks and a 24/7 vendor SLA, leading to adoption of Linkerd with Buoyant enterprise support and guided onboarding that reduces time to production and keeps exit costs low.
AI-written summary · about
chapters (10)
- 0:00Welcome
- 1:02Real problems to solve
- 3:50Why service mesh matters
- 7:02Key evaluation categories
- 10:20Service mesh options and criteria
- 13:31Istio's hidden costs
- 16:23Why Linkerd won
- 19:11Decision framework
- 21:36Team perspectives and biases
- 24:24Final advice
related talks
26mNavigating the Service Mesh Landscape - Paul Bouwer, Microsoft
44mService Mess to Service Mesh
47mService mesh options with Istio, Linkerd, and/or Consul
45mService Mesh War Stories - Lessons Learned the Hard Way
35mRethink About Service Mesh Load Balancing
21mSolving the Service Mesh Adopter’s Dilemma
34mContainer Networking Untangling Services Meshes and SDNs
31mClean-up Your Service Mess with Service Mesh