A service mesh moves controls into the communication layer
A service mesh handles identity, encryption and policy between services, so applications do not each implement it themselves.
That is a real improvement in consistency: one place to enforce mutual authentication rather than hoping every team did it. It is also new infrastructure with its own control plane, its own failure modes and its own privileged position, which is a trade rather than a free gain.
More on Architecture patterns
- A jump host concentrates administrative entryOne plank, every crossing
- A bastion should not become a general-purpose workstationIt only has the one job
- Bulkheads contain failureThe water stops at the wall
- Out-of-band management survives primary-path failureWhen the bridge is out
- A choke point makes control observableEverything through one gap
- A broker can separate clients from powerful credentialsChained to the bench
