> 1. I can have a unified set of metrics for all services, regardless of language/platform or how diligent the team is at instrumenting their apps. But they're

> 1. I can have a unified set of metrics for all services, regardless of language/platform or how diligent the team is at instrumenting their apps. But they're only going to be coarse metrics, like what requests/second. You're still going to be needing application-specific metrics. > 2. I can guarantee zero trust with mTLS, without having to rely on application teams dealing with HTTPs or certificates. I do like the idea of this feature of service meshes. It is a slog to get teams to do this responsibly. But, like I said: fighting Istio to understand why it was RST-ing a connection, for no apparent reason. Not logging errors is worse. Perhaps the idea is sound, but the implementation leaves one desiring more. I should mention the same Istio service mesh above is a SPoF in the cluster it runs in, on account of being a single pod. I can't tell if the people who set it up were clueless, or if that's the default. I suspect probably the latter. > 3., 4., and 5., as well as actually using mTLS in 2. TBH, these are just benefits I've never been able to realize. I'm stuck slogging through the swamp of service mesh marketing and the people who want to bring the light of their savior the service mesh but without actually getting their hands dirty doing the work of deploying it.