News for hackers. Stuff that matters.
Re:A Service Mesh for Kubernetes, Part I: Top-Line Service M... by whalesalad on Wednesday October 05, 2016 @10:52AM (#12644273)
Still trying to get the laymans explanation of linkerd. Is it a drop-in replacement for making service-to-service HTTP calls? AFAIK it's a standalone proxy-like version of Finagle.
Re:A Service Mesh for Kubernetes, Part I: Top-Line Service M... by skMed on Wednesday October 05, 2016 @11:18AM (#12644552)
Right, if I want to rely on Finagle's RPC capabilities, e.g. load balancing, routing, tracing, etc, then my microservice must be JVM based and use the Finagle library. This is a standalone proxy deployed as a 'sidecar' app alongside my service. This allows me to implement the microservice in any language I want and get some of the features listed previously.

Of course you now have another moving part in your system :)

Re:A Service Mesh for Kubernetes, Part I: Top-Line Service M... by olix0r on Wednesday October 05, 2016 @10:55AM (#12644303)
That's basically right. linkerd is a proxy that deals with a bunch of operational things like service discovery, metrics/observability, tracing, load balancing, etc. It's a proxy so that you can deploy one solution across all languages/frameworks without having to modify your code to deal with these things.