Loading content
Load balancing allows for evenly distributing requests across multiple servers, enhancing the availability and scalability of applications. By preventing overload on individual servers, performance is optimized.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Load balancing distributes requests or computing work across resources so a service remains responsive and available.
The approach grew from computer and network engineering as increasing traffic overwhelmed individual servers. Early IP and HTTP practices included techniques such as DNS round robin; modern load balancers combine distribution with health checks and session handling.
Think of several supermarket checkouts: new customers go to available counters, and a closed counter receives none. The dispatcher must know current capacity and reachability.
Requests are assigned to multiple targets by a rule.
Unreachable or failing targets are removed from the pool.
Additional resources can increase capacity and resilience.
Load balancing improves response times and resilience, while requiring suitable rules for state, sessions, and bottlenecks.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.