liveBook · Manning

Service mesh

As explained in Grokking Software Architecture

A service mesh is an infrastructure layer that manages service-to-service communication through dedicated networking components and centralized traffic policies.

A service mesh is an infrastructure layer for managing service-to-service communication with dedicated networking components and centralized traffic policies. Think of it as a set of guards at the internal doors, rather than a single guard at the outer wall. section 11.3.3 section 11.10

In a service mesh, sidecar proxies can handle mutual TLS (mTLS) and service identity automatically. This helps apply Zero Trust in systems that use multiple programming languages or include legacy services. section 11.10

A request between two services

An Order Service needs data from a Customer Service. First, the services use mTLS to verify each other’s cryptographic identities—a two-way badge check. Then the Order Service presents an application token, and the Customer Service checks whether it has the least privilege needed to access the data. section 11.3.3

The two checks do different jobs: mTLS verifies the services’ identities, while authorization checks what the requesting service is allowed to access. Checking both helps limit an intruder’s ability to move between services after an internal compromise. section 11.3.3

How Grokking Software Architecture covers it

How deep it goes
Explains mutual authentication and token authorization through a service request, without detailing mesh configuration.
Examples
Uses a request between order and customer services to illustrate mutual authentication and token validation.
What you can do after
Evaluate/understand how sidecar proxies support internal service authentication and why authorization remains a separate check.
How it connects
Connects service mesh to Zero Trust, mutual TLS, service identity, and least privilege.

Also explained in

Compare how 7 books explain service mesh →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.