Two worlds 3 hype7/25/2023 ![]() ![]() The data plane intercepts calls between services and “does stuff” with these calls the control plane coordinates the behavior of the proxies, and provides an API for you, the operator, to manipulate and measure the mesh as a whole. The proxies are referred to as the service mesh’s data plane, and the management processes as its control plane. It’s nothing more than a bunch of userspace proxies, stuck “next” to your services (we’ll talk about what “next” means in a bit), plus a set of management processes. On to the good stuff! What is a service mesh?įor all the hype, the service mesh is architecturally pretty straightforward. When I need concrete examples I’ll primarily rely on Linkerd, but when there are differences I know about with other mesh implementations I’ll call them out. That said, so I’m going to do my best to leave the editorializing to a minimum (except one section, “Why do people talk so much about this?“, where I’ll unveil some opinions) and I’ll do my best to write this guide in a way that is as objective as possible. (Sorry!) I’m also the CEO of Buoyant, a startup that builds cool service mesh stuff like Linkerd and Buoyant Cloud.Īs you might imagine, I am very biased and have some strong opinions on this topic. I am one of the creators of Linkerd, the very first service mesh project and the project that gave birth to the term service mesh itself. Finally, I’m going to attempt to describe why I think this particular technology has attracted such a crazy level of hype, which is an interesting story in and of itself. I’m going to cover not just the what but also the why and the why now. In this guide I’m going to attempt just that: to provide an honest, deep, engineer-focused guide to the service mesh. But there’s some real, concrete, and important value to the service mesh, if you can cut through all the noise. The service mesh was born in the murky, trend-infested waters of the cloud native ecosystem, which unfortunately means that a huge amount of service mesh content ranges from “low-calorie fluff” to-to use a technical term-“basically bullshit”. Thanks to a strange confluence of events, this phrase has been rolling around the industry like a giant Katamari ball, glomming on successively bigger pieces of marketing and hype and showing no signs of stopping any time soon. If you’re a software engineer working anywhere near backend systems, the term “service mesh” has probably infiltrated your consciousness some time over the past few years. ![]()
0 Comments
Leave a Reply. |