Service Mesh Fatigue in 2026: When to Use One and When to Skip

The CNCF’s 2024 survey recorded production service-mesh adoption falling from 50% to 42%, with operational overhead among the concerns. AWS is also retiring App Mesh on September 30, 2026, so expanding that deployment is a migration decision, not a new-platform choice.

The remaining options are getting simpler. Istio’s ambient mode has been generally available since 1.24; Istio 1.30 adds ambient multicluster beta and experimental agentgateway. Linkerd 2.20 adds rate-limit-aware load balancing, makes native sidecars the default, and reports up to an 85% control-plane memory reduction in some cases. A mesh still needs ownership and observability.

Start with Kubernetes Gateway API for ingress routing, TLS, and ordinary L7 policy. Add a mesh for transparent mTLS across many services, advanced canaries or retries, multi-cluster east-west traffic, or inference routing. If the application is small, mostly monolithic, or lacks a platform owner, skip it. Use the smallest networking layer that solves today’s problem; adopt a mesh when the requirement is real.