Linkerd Deep Dive
summary
Linkerd is put into production as a sidecar to deliver client-side load balancing with connection pooling, circuit breakers and retries, removing external load balancers and cutting costs. SoundCloud routes ~1500 QPS across multiple Elasticsearch clusters with p95 goals under 100 ms and Linkerd shifts traffic away from slow clusters to avoid pages. BigCommerce publishes gRPC service names in Consul and uses a watcher to write DTab-based gRPC routing, letting Linkerd translate gRPC destinations into IP:port and succeed in prod.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:19Introductions
- 2:48Agenda
- 19:35Consistent Service Names
- 20:42Sell your soul to the service mesh
- 21:37Teach Linkerd convert RPC name to IP Port
- 23:46Links !
- 23:57First Steps
- 24:53Architecture
- 25:32Plugins
- 26:28Contribution
related talks
05mKeynote: An update on the extremely boring and uninteresting world of Linkerd
27mThe Future of Linkerd: 2.18 and Beyond
30mProtocol Detection: A Deep Dive into How Linkerd Achieves Zero-Config
30mClusterlink: Enabling Fine-Grained and High-Speed Application-Level Connectivity...
34mContainer Networking Untangling Services Meshes and SDNs
29mgRPC load balancing and Service Mesh
31mClean-up Your Service Mess with Service Mesh
18mDeveloping a Custom Load Balancer to serve traffic at scale