4 ms·
But what in the hell is it? If your product is so revolutionary it defines a new market segment, you might want to bring the people with the money people up to
by dsl 9y ago
But what in the hell is it? If your product is so revolutionary it defines a new market segment, you might want to bring the people with the money people up to speed.
- wiremine 9y agoIt's an "open source service mesh." They're assuming you know what that is, and what their existing product (Linkerd) does in that space. I think that's reasonable for a blog post, and you can go look at their solid documentation if you don't.
- uptown 9y agoThis explanation was helpful to me: https://buoyant.io/2017/04/25/whats-a-service-mesh-and-why-do-i-need-one/ https://buoyant.io/2017/04/25/whats-a-service-mesh-and-why-d...
- treesloth 9y agoHad to google this myself, here's a link to their description of a service mesh. https://buoyant.io/2017/04/25/whats-a-service-mesh-and-why-do-i-need-one/ https://buoyant.io/2017/04/25/whats-a-service-mesh-and-why-d...
- bmurphy1976 9y agoTypically a mesh is a set of proxies that are colocated with each service you deploy. The proxies facilitate service discovery and secure communication with other services. They abstract this functionality such that each service doesn't have to individually (and poorly) reinvent that wheel. Your service would connect to database:5432, but instead of going straight to the database it goes to a proxy and the proxy has all the smarts to find and connect to the database, even if it's in another data center. The proxy can also do it securely such that you can go over the public network if necessary. There's a good chance you don't need this complexity, but if you are hosting 100's of small services across multiple cloud providers, regions, or data centers, this starts to become an attractive option.
- dsl 9y agoI just force every application to use a standard reliable transport library. Didn't realize I built a service mesh startup by accident...