3 ms·

Lyft has a tech similar to linkerd called Envoy: https://github.com/lyft/envoy https://github.com/lyft/envoy. It is a bit lower level than linkerd (based on API

Lyft has a tech similar to linkerd called Envoy: https://github.com/lyft/envoy https://github.com/lyft/envoy. It is a bit lower level than linkerd (based on APIs rather than already integrated with common services) and written in C++. I'm working on an adapter which should offer a better integration with Kubernetes. The end goal is to have envoy be able to replace our Ingress controllers. Not having to run the JVM on every machine is also nice.

stock_toaster 10y ago
> Not having to run the JVM on every machine is also nice. Personally, Envoy compiling to a binary makes it much more likely that I would experiment with it than with linkerd. I have hesitated trying out linkerd because we don't run anything JVM based in any of our stack, and we aren't currently excited about introducing any. I am definitely going to take a look at Envoy. Thanks for referencing it!
zweizeichen 10y ago
Folks at Lyft/IBM/Google are building a service mesh partly based on Envoy over here: https://istio.io https://istio.io