undefined | Better HN

0 pointswilliamallthing6y ago0 comments

Yes, you pay a latency and resource cost to have the service mesh features decoupled from the application code. Same with any abstraction e.g. containers or Kubernetes.

You could alternatively get service mesh features in the application layer with libraries like Finagle, Hysterix, etc, and not pay that cost. But then you're tied to particular languages, and changing platform features requires making code changes.

It's a tradeoff. I talked about this at Kubecon earlier this year: https://www.youtube.com/watch?v=Z3nfLI3z0hc#t=4m58

0 comments

aashishkoirala6y ago

That was a great talk, thanks for sharing. I guess it all makes sense once you have bought into having synchronous dependencies between microservices - which is the part I was struggling with. But I guess if that is what you have to do, that is what you have to do.

j / k navigate · click thread line to collapse

0 pointswilliamallthing6y ago0 comments

Yes, you pay a latency and resource cost to have the service mesh features decoupled from the application code. Same with any abstraction e.g. containers or Kubernetes.

It's a tradeoff. I talked about this at Kubecon earlier this year: https://www.youtube.com/watch?v=Z3nfLI3z0hc#t=4m58

0 comments

aashishkoirala6y ago

j / k navigate · click thread line to collapse