Open Source Summit + Embedded Linux Conference North America 2026

Microservices promised speed and independence, but for many SREs and developers, they delivered network complexity. Suddenly, we're all part-time network engineers. We have to code retry logic, timeouts, and circuit breakers into every service. We struggle to get uniform "golden signal" metrics. And how do we enforce that all 50 of our polyglot services are communicating securely over mTLS?

This is the "microservice tax," and it's holding us back.

Enter the service mesh. You've heard the buzzwords, Istio, Linkerd, but what is a mesh, and what problems does it actually solve? Is it just hype, or is it the key to taming a complex distributed system?

We'll cover the three pillars of a mesh:

Reliability: Automatic retries, timeouts, and circuit breakers.

Observability: Uniform metrics, logging, and tracing for every call.

Security: Automatic mTLS (encryption) and fine-grained authorization policies.