Load Balancing¶
Distribute incoming work across multiple viable receivers by capacity, health, or policy so no part is overloaded while usable capacity sits idle.
The Diagnostic Story¶
Symptom: Some receivers are saturated while others sit idle, and the system behaves as if capacity is scarce even though total capacity may be adequate. One server is overloaded while five others handle almost nothing. One team absorbs every request because it is the most visible. One region, warehouse, or service desk becomes a hot spot while equivalent alternatives are underused.
Pivot: Change how work is assigned. Route, distribute, or redirect incoming flow across multiple viable receivers according to a policy that accounts for capacity, health, load, locality, or priority. The key move is not simply splitting evenly; it is sending work where it can actually be handled.
Resolution: Localized overload declines as idle capacity is put to use and the distribution policy adapts to receiver health and load. The balancing layer does not drop work, and unhealthy receivers are removed or downweighted. Total demand is unchanged, but poor assignment is no longer making the system behave as if capacity were insufficient.
Reach for this when you hear…¶
[platform SRE] “Two of our six nodes are at one hundred percent and the other four are doing nothing because the load balancer is still sending everything to the first healthy response.”
[hospital intake] “The ER is on diversion while the urgent care centers nearby have open beds, so we need to route patients differently rather than just expanding the ER.”
[workforce management] “Half the team is drowning in tickets while the other half has been sitting at sixty percent capacity for weeks because we never looked at the assignment queue.”
When This Archetype Applies¶
No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.
Diagnostic problem
Demand is unevenly concentrated on some receivers while other viable parallel capacity remains underused.
Show the applicability expression
Applicability expression1 distinct condition
groundedpartly groundedopen
1 condition, all required.
1Required in every casenumbered 1–1
These hold no matter which pattern applies.
Concentrated workload imbalance · open
Demand or workload is unevenly concentrated on one or more receivers while other viable capacity is underused.
This proposition-sized condition was conservatively reconstructed from the authored essence_one_line, compression_statement, components fields; the source file was not modified. In this condition set, the requirement is: Demand or workload is unevenly concentrated on one or more receivers while other viable capacity is underused.
Other requirements and context (1)
Why these sit outside the expression
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Solution feasibilityThe work can be divided or reassigned among multiple receivers.
This proposition-sized condition was conservatively reconstructed from the authored essence_one_line, compression_statement, components fields; the source file was not modified. In this archetype, the relevant feasibility condition is: The work can be divided or reassigned among multiple receivers. It identifies something that must be possible or available for the intervention to be workable.
Coverage
0 of 1 conditions grounded · 1 open.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (8)
- Admission Control
- Capacity Signal
- Distribution Policy
- Feedback: Outputs influence inputs.
- Health Check
- Monitoring: Continuously observing a system's state to detect deviation from expected behavior and trigger a response, separating genuine signal from routine noise.
- Resource Pooling
- Routing Rule
Also references 13 related abstractions
- Constraint: Limits possibilities to guide outcomes.
- Coupling: Interdependence among subsystems.
- Fairness: Judging whether an allocation or procedure treats comparable parties impartially according to a defensible standard, given that multiple such standards can conflict.
- Flow: Structured movement of energy, matter, or information.
- Network: Models interactions between components.
- Observability: Infer internal state externally.
- Queueing: Organizes tasks into a waiting line based on arrival and service rates.
- Resilience: Absorb shocks and adapt.
- Resource Management: Allocation of finite assets.
- Robustness: Maintain functionality under stress.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Capacity-Aware Routing · implementation variant · recognized
Route work or flow based on current or expected capacity across multiple receiving paths.
Symmetric Parallel Load Addition And Reaction Cancellation · implementation variant · recognized
Divide a high-load transmission into matched parallel paths and recombine them symmetrically so capacity adds while transverse reactions partially cancel.
Editorial Notes¶
Problem Classification¶
Classification: Congestion, Backlog & Flow Breakdown → Routing, Distribution & Endpoint Failure
Problem kernel: routing overloads some receivers while viable capacity remains idle
Rationale: Both reviewers identify the same flow defect: work pools on overloaded receivers while other viable capacity remains idle because routing does not account for receiver capacity, health, or policy. Assimilation overload describes what happens at the saturated receiver, but the earlier system-level cause is distribution failing to use available endpoints.
Boundary considered: Capacity Scarcity & Resource Contention → Assimilation Saturation & Overload
Why this classification prevailed: Routing failure concerns uneven distribution despite idle viable endpoints; assimilation overload concerns a bounded receiver exceeding its processing ceiling regardless of alternate routing capacity.
Review outcome: Reconciled after independent review; high confidence.