| Those quotes aren't from the article. I'll address them anyways since they're from a different article which I wrote: >> "Traditional service meshes are an all-or-nothing proposition that add a significant layer of complexity to your stack. That’s not great." > Istio is like k8 it's very modular and you setup what you need. Istio is a very different beast from Linkerd. But out of curiosity, I just tried the latest Istio release on my laptop (1.0.2 on Docker for Mac K8s). The simplest configuration I found installs 50 (!) CRDs, 13 deployments, and is currently sitting at ~600mb of memory without any traffic. Perhaps by "modular" you mean you can add more modules on top of that? (By contrast, Linkerd 2.0 installs 0 CRDs, 4 services, and is sitting at 250mb including 50mb full Grafana UI. It also does a lot less... but that's the point.) That's the control plane. Let's not get started on the data plane. >> "Traditional service meshes are designed to meet the needs of platform owners, and they dramatically underserve a more important audience: the service owners." > Not sure what it means, Istio is all about observability ect... This is all in the article. You can install Linkerd as a service owner on a single service. You'll get metrics, debugging, and more. It's lightweight and small enough for this installation make sense. Try it. You might just like it :) |