[EN] update load balancer #2995
Open
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
Signed-off-by: Fitsum Sileshi <fitsesile@gmail.com>
FII78
requested review from
caniszczyk,
seokho-son,
iamNoah1,
jihoon-seo,
nate-double-u and
castrojo
as code owners
✅ Deploy Preview for cncfglossary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
iamNoah1
requested changes
Apr 4, 2024
| Take a [microservice](/microservices/) architecture for example, where each service can be [scaled horizontally](/horizontal-scaling/). | ||
| A load balancer sits in front of a scaled microservice and ensures that no one instance gets the bulk of the requests. | ||
| Load balancers can be software or hardware-based. | ||
| A load balancer is a crucial component in computer networks that distributes incoming requests across multiple servers. By doing so, it prevents any single server from becoming overwhelmed, ensuring consistent and reliable performance for users accessing websites or applications. |
There was a problem hiding this comment.
I would suggest to use instances of an application instead of servers here and in the following content.
There was a problem hiding this comment.
To be super honest, I don't find the new text providing more clear information. I find the old text better.
| To handle all those requests, applications are often scaled horizontally. | ||
| But horizontal scaling introduces a new challenge. How do you distribute incoming traffic to all services equally? | ||
| This is where load balancers come in. | ||
| Managing network traffic distribution across multiple servers or instances is a complex task, particularly in large-scale applications. Without an automated solution, maintaining high availability, efficient resource utilization, and seamless [scaling](https://github.com/ronitblenz/glossary/blob/cloud_computing/content/en/scalability.md) becomes challenging. Load balancers address this problem by automating the distribution of incoming requests, ensuring [reliability](https://github.com/cncf/glossary/blob/main/content/en/reliability.md), and enhancing system performance. |
There was a problem hiding this comment.
This section is nice :), please lets just take the last sentence and put it in the last section, because here we don't want to talk about how the problem is solved. Also please have a look how to correctly reference other terms.
| Load balancers dynamically distribute all incoming requests among multiple services, ensuring that no one service gets the bulk of it while others only get a few or none. | ||
| In short, it spreads the load across multiple services, following a defined schema (i.e., evenly or percentage-based). | ||
| Load balancers are essential to an application's overall performance and, ultimately, the user experience. | ||
| Load balancers enable users to define the desired state of a system. Initially, they specify the system’s configuration (e.g., number of servers, pods, etc.). Subsequently, the load balancer continuously monitors the infrastructure and automatically corrects any deviations from the intended state (e.g., by spinning up new servers if one fails). This streamlined automation simplifies critical operational tasks, including provisioning, deployment, scaling, networking, and load balancing, which would otherwise be labor-intensive and intricate for engineering teams. |
There was a problem hiding this comment.
This whole section is not really describing how load balancers solve the before mentioned problem. You are describing something like kubernetes here.
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.
Describe your changes
Update term load-balancer
Related issue number or link (ex:
resolves #issue-number)resolves #2519
Checklist before opening this PR (put
xin the checkboxes)git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to yourgitconfigby runninggit config --global alias.ci "commit -s".