Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparison to linkerd #99

Closed
jparise opened this issue Sep 26, 2016 · 8 comments
Closed

Comparison to linkerd #99

jparise opened this issue Sep 26, 2016 · 8 comments

Comments

@jparise
Copy link
Contributor

jparise commented Sep 26, 2016

The documentation's comparison list is both thorough and useful. Thanks for that!

Would you consider adding a brief comparison to linkerd? It's based on Finagle, so I would expect the existing section to cover most of the details, but as a proxy product, linkerd is even more similar to Envoy (and a competitor).

@mattklein123
Copy link
Member

Sure, we can add a comparison.

@olix0r let me know if you or someone from Bouyant wants to write the comparison. You can email me offline to discuss if you want. Otherwise I will write it.

@olix0r
Copy link

olix0r commented Sep 26, 2016

Thanks for looping me in, @mattklein123. I'll talk to the team this morning and find a volunteer.

@olix0r
Copy link

olix0r commented Sep 30, 2016

Here's what we came up with:

linkerd is a standalone, open source RPC routing proxy built on Netty and Finagle. linkerd offers many of Finagle’s features, including latency-aware load balancing, connection pooling, circuit-breaking, retry budgets, deadlines, tracing, fine-grained instrumentation, and a traffic routing layer for request-level routing. linkerd provides a pluggable service discovery interface (with standard support for Consul and ZooKeeper, as well as the Marathon and Kubernetes APIs).

linkerd’s memory and CPU requirements are significantly higher than Envoy’s. However, its underlying tech is extensively production tested and widely deployed. In contrast to Envoy, linkerd provides a minimalist configuration language, and explicitly does not support hot reloads, relying instead on dynamic provisioning and service abstractions. linkerd supports HTTP/1.1, Thrift, ThriftMux, HTTP/2 (experimental) and gRPC (experimental).

If there's anything else you think should be addressed, just let us know!

@mattklein123
Copy link
Member

Sure that sounds fine. I will do a PR to get it in.

@mattklein123
Copy link
Member

#145

@jamiely
Copy link

jamiely commented Dec 21, 2017

The comparison is now at https://www.envoyproxy.io/docs/envoy/latest/intro/comparison for those coming from search engines.

rlenglet referenced this issue in istio/envoy Aug 13, 2019
Signed-off-by: John Plevyak <jplevyak@gmail.com>
PiotrSikora pushed a commit to PiotrSikora/envoy that referenced this issue Aug 27, 2019
fix upstream host NULL pointer
@rafaelcaricio
Copy link

All comparison pages are gone now. Where can we get a link to a comparison?

@moderation
Copy link
Contributor

Maintaining accurate comparisons is time consuming. There are a number of third party sites that provide this information like https://layer5.io/landscape

jwendell pushed a commit to jwendell/envoy that referenced this issue Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants