The Crazy Service Mesh Ecosystem

on YouTube ↗20m

" summary

Overview enumerates actual implementations and tradeoffs and names concrete numbers and behaviors rather than vague benefits. Istio 1.x: ~300 companies ~400 contributors and rich feature set built on Envoy: used in 100+ services across ~10,000 VMs, Linkerd 2.0 rewrites the sidecar in Rust and defaults to mutual TLS and 2–3 automatic retries. AWS App Mesh maps to ECS Fargate EC2. Live demos are promised but are not fully completed in the session.

AI-written summary · about

" chapters (14)

1. 0:00Start
2. 0:09The Crazy Service Mesh Ecosystem
3. 5:23A Service Mesh is...
4. 6:29Before Service Mesh
5. 7:31Key Benefits
6. 8:48Navigate the Ecosystem
7. 9:36Key Service Mesh Players
8. 10:16Envoy
9. 11:59Istio
10. 14:30Namespace: linkerd
11. 14:53Consul Connect
12. 16:11Kong Kuma
13. 16:37Aspen Mesh
14. 17:06Service Mesh Interface

" related talks

• 35mNavigating the Service Mesh EcosystemGeorge Miranda, Diogenes Rittori · KubeCon + CloudNativeCon China 2018
• 40mComparison of Current Service Mesh ArchitecturesBruce Basil Mathews · Open Source Summit + Embedded Linux Conference North America 2019
• 43mWTF Do We Need a Service Mesh?Anton Weiss · Cloud Native & OSS Day Tel Aviv 2019
• 34mService Mess to Service MeshRob Richardson · Conf42 Kube Native 2023
• 11mWelcome & Opening RemarksChristian Posta · ServiceMeshCon Europe 2020
• 01h 03mJust what is a "service mesh", and if I get one will it make everything OK?Elton Stoneman · NDC London 2019
• 28mService Mesh: Demystifying IstioJeferson Fernando · DevOpsDays Vitória 2020
• 34mService Mess to Service MeshRob Richardson · DevOpsDays Boston 2020