“Microservices on Kubernetes need a service mesh.” You will hear this stated as if it were a law of nature. It is not. A mesh solves a specific set of problems, and if you do not have them yet, it is a heavy thing to carry. Let us take the belief apart in pieces.

What a mesh is, concretely

When service A calls service B, a lot of logic surrounds that call: encrypt the traffic, prove who A is, retry on a transient failure, time out after two seconds, spread requests across B’s instances, record how long it took. Without a mesh, each team implements this in application code, usually through a library, usually differently in the Java services than in the Node ones.

A service mesh moves that logic out of the application and into the network layer. The classic design runs a small proxy (Envoy is the common one) next to every application instance, as a “sidecar” container in the same Kubernetes pod. All traffic in and out passes through that proxy. A separate control plane, such as Istio or Linkerd, tells the proxies what rules to follow. Your code just makes a plain call; the proxy does the rest.

Belief one: a mesh is only about routing

Routing is the least interesting part. The real features are these:

  • Mutual TLS between services. Both sides present certificates, so traffic inside the cluster is encrypted and each service knows who is calling. The mesh issues and rotates the certificates, which is tedious to do by hand.
  • Traffic policy. Send 5 per cent of requests to the new version of a service while 95 per cent go to the old one, which makes canary releases a configuration change.
  • Resilience defaults. Uniform timeouts, retries and circuit breaking, without each team re-implementing them.
  • Uniform telemetry. Request counts, error rates and latency between every pair of services, for free, including services written in languages nobody wanted to instrument.

The value is consistency across many services and many teams. That is where the strongest case lies: a hundred services in four languages, a compliance requirement for encryption in transit everywhere, and a platform team that can own the mesh.

Belief two: it is free once installed

Every sidecar uses CPU and memory. Multiply a modest allocation by hundreds of pods and it shows up on the cloud bill. Every call gains two extra proxy hops, one on each side, adding a little latency; usually small, but measurable on chatty call chains. The control plane is another system to upgrade, and mesh upgrades touch every workload. When something fails, you now have a new place to look: is it the application, the proxy configuration, the certificate, the policy? Engineers who did not choose the mesh end up debugging it at 2 am.

Newer designs try to reduce this. Istio has an “ambient” mode that avoids per-pod sidecars by using node-level proxies, and Cilium offers mesh features built on eBPF in the kernel. These shift the trade-offs, but they do not remove the operational weight; you still run and understand a new layer.

Belief three: a mesh fixes unreliable services

It does not. Automatic retries on a service that is already overloaded make the overload worse, a retry storm. Retrying a request that is not idempotent, such as “create payment”, can charge someone twice; the mesh cannot know the difference, so someone must configure retries per route with care. A mesh also cannot fix slow database queries, poor data models or chatty service designs. It makes the network between services better behaved. It does not make the services better.

What you can do without one

Before adopting a mesh, check whether cheaper tools cover the need.

  • For retries and timeouts in a handful of services, a well-tested shared library or the HTTP client configuration is enough.
  • For canary releases, an ingress controller or a deployment tool such as Argo Rollouts can split traffic.
  • For encryption in transit, terminating TLS at the edge plus network policies may satisfy your actual requirement; check what your auditors really ask.
  • For observability, OpenTelemetry instrumentation in the code gives richer data than proxy metrics, since proxies only see the network.

A reasonable test

Consider a mesh when most of these are true: you run dozens of services across several teams and languages; you need identity-based, encrypted service-to-service traffic as a firm requirement; inconsistent resilience settings have already caused an outage; and a team exists whose job is to run the platform. If you have six services and two backend teams, the more likely truth is that you need a better deployment pipeline and a few shared library standards, and a mesh would be a second job on top of the first.

Also try it in a non-production cluster first and measure the overhead on your own workloads. Numbers from a vendor benchmark describe the vendor’s workload, not yours.

Leave a Reply

Trending