-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Comments
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. |
Thanks for looping me in, @mattklein123. I'll talk to the team this morning and find a volunteer. |
Here's what we came up with:
If there's anything else you think should be addressed, just let us know! |
Sure that sounds fine. I will do a PR to get it in. |
The comparison is now at https://www.envoyproxy.io/docs/envoy/latest/intro/comparison for those coming from search engines. |
Signed-off-by: John Plevyak <[email protected]>
fix upstream host NULL pointer
All comparison pages are gone now. Where can we get a link to a comparison? |
Maintaining accurate comparisons is time consuming. There are a number of third party sites that provide this information like https://layer5.io/landscape |
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).
The text was updated successfully, but these errors were encountered: