Are envoy and linkerd comparable? They look like they fill similar niches, but I'm not familiar enough to know what I don't know.
Also see: eBay/fabio, Traefik.io .
Envoy: 7 months later
11–20 of 48 posts
Re: Envoy: 7 months later
#12We've been experimenting with Envoy for a few months and have been really impressed with the technology and the responsiveness of the community. We're actually deploying an API Gateway built on Envoy so you can easily extend your service mesh all the way out to the edge. Planning on open sourcing it soon (if anyone wants to give it a try, my email is in my profile).
Re: Envoy: 7 months later
#13Re: Envoy: 7 months later
#14Re: Envoy: 7 months later
#15Earlier quoted context omitted.
This. Linkerd has been a pretty cool piece of tech. In fact, their rewrite linkerd-tcp is in Rust and is blazingly fast. Also, it works on L4 and can do more stuff than Envoy... though I think that advantage is going to be shortlived. Linkerd guys have been focusing on building deep integration with k8s (as an ingress or sidecar), but this announcement of Envoy trumps it all. > "We are excited to announce that we are…
Isn't linkerd in Scala and linkerd-tcp a small subset of it?
That's correct. linkerd/namerd run on the JVM.
Re: Envoy: 7 months later
#16Interesting that it seems like there is a bunch of overlap with linkerd in the k8s space. With both k8s and linkerd being CNCF projects, I wonder why google is putting so many resources behind envoy rather than linkerd. I guess that's the beauty of the k8s ecosystem though, freedom and choice to use what you see fit. K8s just provides the rock-solid primitives.
Re: Envoy: 7 months later
#17We've been experimenting with Envoy for a few months and have been really impressed with the technology and the responsiveness of the community. We're actually deploying an API Gateway built on Envoy so you can easily extend your service mesh all the way out to the edge. Planning on open sourcing it soon (if anyone wants to give it a try, my email is in my profile).
Any reason you chose to use API Gateway for your edge instead of another Envoy with an ELB in front?
Re: Envoy: 7 months later
#18Looks interesting except imo the configuration makes it basically unusable.
They use jinja2 templated json... and there are hundreds of lines for their "simple" examples.
Even the "hello world" type example of proxying to google is a mess https://github.com/lyft/envoy/blob/master/configs/google_com...
Re: Envoy: 7 months later
#19We've been experimenting with Envoy for a few months and have been really impressed with the technology and the responsiveness of the community. We're actually deploying an API Gateway built on Envoy so you can easily extend your service mesh all the way out to the edge. Planning on open sourcing it soon (if anyone wants to give it a try, my email is in my profile).
Any reason you chose to use API Gateway for your edge instead of another Envoy with an ELB in front?
Sorry, I wasn't clear. I was referring to using Envoy as an API gateway, not a specific API gateway product. We had to write some wrapper code on top of Envoy that lets you use a REST API to map URLs to services running in your Kube cluster and then dynamically update Envoy config, etc.
Re: Envoy: 7 months later
#20Looks interesting except imo the configuration makes it basically unusable. They use jinja2 templated json... and there are hundreds of lines for their "simple" examples. Even the "hello world" type example of proxying to google is a mess https://github.com/lyft/envoy/blob/master/configs/google_com...
The example you linked isn't so bad. Perhaps a bit verbose for a simple example. The formatting of the json is ugly though, and I think they would do better to not collapse the whitespace inside arrays.