-
Notifications
You must be signed in to change notification settings - Fork 865
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
Proxy supports multiple algorithms for load balancing across destinations #58
Comments
Current implementation: reverse-proxy/src/ReverseProxy.Core/Service/Proxy/LoadBalancer.cs Lines 21 to 36 in be96d64
Note that load balancing is configurable per backend set. Do we need that level of granularity, or could this be specified server wide? |
Oh it should definitely be per backend. It's very common for different services to have different load profiles and benefit from different kinds of load balancing. It's also something Envoy configures per-cluster which serves as some prior art. |
Another one: Least busy |
Is it possible to add a feature for blue green deployment to load balancer? or is it out of the scope of load balancer? |
I think that's a different feature from load balancing that would be handled earlier at the routing phase. Load balancing assumes all nodes are equivalent, plus or minus health/load. |
I'm going to break this up into smaller issues for individual algorithms. @Tratcher and I were talking about some of them being fairly easy and high-value for preview 1 (while others are more complicated). |
Complete the set of common load balancing schemes
First healthy endpoint(already implemented)The text was updated successfully, but these errors were encountered: