Envoy and Linkerd Project Proposal #69
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
venilnoronha
reviewed
Feb 6, 2019
README.md
Outdated
| ### Linkerd and Envoy | ||
|
|
||
| Linkerd is an ultralight service mesh for Kubernetes and beyond: https://linkerd.io. | ||
| Envoy is an open source edge and service proxy, designed for cloud-native applications: https://www.envoyproxy.io |
There was a problem hiding this comment.
nit: end the line with a period, like above.
README.md
Outdated
|
|
||
| #### Benchmarks for Linkerd and Envoy | ||
|
|
||
| - Description: Linkerd, like other service meshes are plagued by the question of adopters asking the question: "what's the performance overhead of the service mesh?". Enovy does not public performance test results [see How fast is Enovy](https://www.envoyproxy.io/docs/envoy/latest/faq/how_fast_is_envoy)). Linkerd, Istio, Enovy and the list of other service meshes don't have a consistent set of performance benchmarks between them. So, even if Envoy were to publish performance results, users still wouldn't be able to compare overhead between Linkerd and Envoy. The project idea here is to build a multi-mesh performance benchmark tool. |
README.md
Outdated
|
|
||
| #### Benchmarks for Linkerd and Envoy | ||
|
|
||
| - Description: Linkerd, like other service meshes are plagued by the question of adopters asking the question: "what's the performance overhead of the service mesh?". Enovy does not public performance test results [see How fast is Enovy](https://www.envoyproxy.io/docs/envoy/latest/faq/how_fast_is_envoy)). Linkerd, Istio, Enovy and the list of other service meshes don't have a consistent set of performance benchmarks between them. So, even if Envoy were to publish performance results, users still wouldn't be able to compare overhead between Linkerd and Envoy. The project idea here is to build a multi-mesh performance benchmark tool. |
README.md
Outdated
|
|
||
| - Recommended Skills: Golang, JavaScript, Kubernetes | ||
| - Mentor(s): Lee Calcote (@leecalcote) | ||
| - Issue: https://github.com/envoyproxy/envoy/issues/5536 and https://discourse.linkerd.io/t/linkerd-performance/146 |
There was a problem hiding this comment.
nit: replace leading tabs (after -) with spaces in the lines above.
venilnoronha
reviewed
Feb 6, 2019
README.md
Outdated
|
|
||
| #### Benchmarks for Linkerd and Envoy | ||
|
|
||
| - Description: Linkerd, like other service meshes are plagued by the question of adopters asking the question: "what's the performance overhead of the service mesh?". Envoy does not publish performance test results [see How fast is Enovy](https://www.envoyproxy.io/docs/envoy/latest/faq/how_fast_is_envoy)). Linkerd, Istio, Enovy and the list of other service meshes don't have a consistent set of performance benchmarks between them. So, even if Envoy were to publish performance results, users still wouldn't be able to compare overhead between Linkerd and Envoy. The project idea here is to build a multi-mesh performance benchmark tool. |
There was a problem hiding this comment.
Thanks, @venilnoronha. It only took me 5 commits to learn how to spell Envoy.
@venilnoronha awesome. Yes, there is. I'll message to brainstorm with you. |
|
@leecalcote sounds great! Thanks! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.