Skip to content
BENIBIX Learn

Service Mesh

Development🏗️ ArchitectureDistributed Systems

Also known as Sidecar Proxy, Mesh

Small helpers sit next to each service. They handle the calls between them.

Think of it like

Think of it like giving each worker a helper. The helper takes their mail and keeps track of it.

Example

Lucy's company runs 120 services. With a service mesh, every call between them is encrypted and measured, and no team had to change its code.

Why it matters

Each service gets the same safety and the same view. No team has to build it again.

Definition

A service mesh is a layer that handles the traffic between services. The services do not have to. Next to each service runs a small proxy, often called a sidecar. All calls in and out pass through these proxies. They add encryption, retries, timeouts and traffic numbers without any change to the app code. It is mostly used when a company runs dozens or hundreds of services.

Common mistake

Adding a mesh to a handful of services. It brings many moving parts that a small system does not need.

Key takeaways

  1. 1
    A proxy per service. The sidecar.
  2. 2
    Handles the traffic. Encryption, retries, numbers.
  3. 3
    For many services. Not a handful.

Compare