The process of distributing computational tasks, connections, or requests across multiple servers or resources to improve throughput, reduce response time, and increase availability and resource utilization.

Principle

Assign work to resources using policies (round-robin, least-connections, weighted, consistent hashing, metric-driven) that account for resource capacity, state, and policy goals (latency, fairness, affinity).

Demonstration

A load balancer routes incoming HTTP requests among a pool of web servers using least-connections while health checks remove unresponsive servers; consistent hashing assigns cache keys to backend nodes minimizing remapping when nodes join or leave.

Misapplication

Using simple round-robin without accounting for server heterogeneity or sticky sessions that force many requests to one server, causing hotspots and degraded performance; ignoring health leads to routing to failed nodes.

Consequence

Proper load balancing increases throughput, lowers tail latency, and improves fault tolerance; it enables elastic scaling and maintenance without service interruption when combined with health and capacity awareness.

Reversal

Concentrating all requests on a single server or evenly distributing without regard to capacity can create bottlenecks and single points of failure, reducing overall system throughput and resilience.

Boundary

Applies to distributing requests and tasks across multiple computational or network resources; does not automatically perform autoscaling, scheduling for long-running batch jobs, or application-level consistency management.

Semantic Tension

Overlaps with scheduling and autoscaling: schedulers optimize resource assignment over time and autoscaling changes capacity; load balancing focuses on runtime routing and distribution to existing resources.

Synthesis

Load balancing is the runtime decision process that maps incoming work to available resources using routing policies and health/metric feedback to optimize utilization, latency, and availability.