Service Mesh
An infrastructure layer of sidecar proxies that handles service-to-service traffic — retries, mTLS, observability — without touching application code.
A service mesh deploys a lightweight proxy (a sidecar) alongside every service instance, and routes all inter-service traffic through these proxies instead of directly between application processes. That gives you consistent retries, timeouts, mutual TLS, load balancing, and observability across every service in the mesh — configured centrally, uniformly — without changing a line of any individual service’s code.