What a Service Mesh Is
A service mesh is a dedicated infrastructure layer that handles communication between services. Instead of baking retries, timeouts, encryption, and metrics into every application, the mesh moves that logic into a network layer that runs alongside your code.
The Core Idea
- Decoupling: networking concerns live outside business logic.
- Uniformity: every service gets the same security and observability for free.
- Language agnostic: a Java service and a Go service behave identically on the wire.
A mesh has two parts. The data plane carries the actual traffic, usually through proxies next to each service. The control plane configures those proxies and holds the policy.
When You Need One
Small systems with three services rarely need a mesh. The value grows with the number of services, because hand written networking code drifts and duplicates. A mesh centralizes that effort.
The trade off is operational weight. You add proxies, latency, and a control plane to run. For large microservice fleets that cost pays off.
Key idea
A service mesh lifts retries, encryption, and metrics out of every app and into a shared layer of proxies steered by a control plane.