Copy this bookmark:



bookmark detail

The Service Mesh: What Every Software Engineer Needs to Know about the World's Most Over-Hyped Technology
Good overview from the author of [Linkerd](

> If you’re encountering the idea of service mesh for the first time, you can be forgiven if your first reaction is mild horror. The design of the service mesh means that not only does it add latency to your application, it also consumes resources and also introduces a whole bunch of machinery. One minute you’re installing a service mesh, the next you’re suddenly on the hook for operating hundreds or thousands of proxies. Why would anyone want to do this?
> There are two parts to the answer. The first is that the operational cost of deploying these proxies can be greatly reduced, thanks to some other changes that are happening in the ecosystem. Lots more on that later.
> The more important answer is because this design is actually a great way to introduce additional logic into the system. That’s not only because there are a ton of features you can add right there, but also because you can add them without changing the ecosystem. In fact, the entire service mesh model is predicated on this very insight: **that, in a multi-service system, regardless of what individual services actually do, the traffic between them is an ideal insertion point for functionality.**

Service mesh is on a maximum in the [hype cycle](
november 2019 by thingles
view in context