Re:K8s Service Meshes: The Bill Comes Due
by lukeschlather on Saturday March 02, 2024 @01:46AM
(#39570443)
I really hate this pattern in principle, but it isn't as bad as you're making it out to be. Most of the service meshes operate as sidecars, which is to say that if service A is calling service B through a mesh, there are two proxies in between the services, but proxy A is on the same machine as A, and proxy B is on the same machine as proxy B. So it is kind of offensive to have 3 network hops involved, but actually only one of those is over the wire, and in most cases I don't think the proxies are actually causing any measurable latency. (At least, whatever latency it's causing is smaller than the latency caused by the TLS encryption, which is necessary and the whole point.)
[ Parent
| on HN ]
Re:K8s Service Meshes: The Bill Comes Due
by phildenhoff on Saturday March 02, 2024 @02:18AM
(#39570614)
That makes sense! I didn't realise the proxies were sidecars, but that seems obvious in retrospect.