What Do Service Meshes Actually Solve? (William Morgan, Buoyant/Linkerd)

Network calls fail in ways function calls never do - and once a monolith becomes microservices, reliability problems show up fast: retries amplify load, latency spikes cascade, and “what talks to what?” becomes hard to answer.William Morgan, co-creator of Linkerd and the person who coined “service mesh,” breaks down what service meshes actually solve for platform teams running Kubernetes at scale. The conversation focuses on practical outcomes: improving reliability between services, getting uniform observability without rewriting every app, and handling gaps Kubernetes doesn’t cover well - like gRPC/HTTP2 load balancing and cross-environment communication.Key topicsWhy reliability is the first “microservices tax” (timeouts, retries, backoff, cascading failure)What Kubernetes does not solve at the networking layer—and where a service mesh fitsgRPC/HTTP2 load balancing problems and why L4 balancing can fall shortService-to-service visibility: understanding traffic flows and performance without per-app instrumentationCost and resilience tradeoffs with multi-AZ Kubernetes on AWS (and how zonal-aware balancing can help)Whether developers should ever need to interact with service mesh configurationWhere zero trust and policy controls belong: platform guardrails vs application ownershipGuest: William Morgan, CEO at Buoyant, Co-Creator of LinkerdWilliam Morgan brings a unique take on platform engineering, security, and traffic management in cloud native environments. William’s the mind behind Linkerd, the CNCF graduate service mesh born to make security, observability, and reliability "just work" for modern apps without all that heavy overhead. With roots as an infrastructure engineer at Twitter, where he was hands-on in the shift to microservices, and experience at Microsoft, Powerset, Adap.tv, and MITRE, William understands operational complexity better than most. His perspective on reducing unpredictable cloud spend with features like Linkerd’s High Availability Zonal Load Balancing is timely for any team wrestling with multi-AZ cloud bills.William has hands-on knowledge of MCP, the protocol now critical for securing enterprise AI traffic. He also has strong views on sustainable open source business models, having contributed to open source for over 20 years.William Morgan, BlueSkyBuoyant, WebsiteBuoyant, LinkedInBuoyant, YouTubeLinkerd, GitHubLinks to interesting things from this episode:The Service Mesh Landscape