A service mesh is an infrastructure layer that handles communication between microservices: routing, encrypted traffic (mTLS), automatic retries, timeouts, traffic splitting and metrics collection, without changing application code.
In its classic form, a small proxy (often Envoy) runs next to each service as a sidecar. Every call goes through it. A central control plane distributes rules to all the proxies. Newer approaches drop the sidecar and move this work to the node or Linux kernel level (Istio's Ambient mode, eBPF-based Cilium).
The best-known implementations are Istio, Linkerd and Consul. A service mesh is justified when the number of services makes security and network visibility unmanageable by hand. On a small architecture, it mostly adds complexity.
Why it matters when hiring
This is a topic for a Platform Engineer, SRE or senior DevOps running Kubernetes at scale. Ask why the team adopted a service mesh, what it cost to operate and how they debug a failing call between two services. Be wary of a candidate who recommends it everywhere: being able to say "not yet" is a sign of maturity.
