What is Load Balancing?

Table of Contents 5 sections

What is Load Balancing?

Load balancing is a critical infrastructure technique that distributes incoming network traffic, application requests, or workloads across multiple servers or resources. The primary goal is to ensure that no single server bears too much demand, which prevents bottlenecks, reduces response times, and maximizes throughput. A load balancer acts as a traffic controller, sitting in front of a group of servers and routing client requests to the most appropriate server based on predefined algorithms and real-time conditions.

In modern web infrastructure, load balancing is essential for maintaining high availability and reliability. By distributing traffic across multiple servers, load balancers ensure that if one server fails or becomes unresponsive, traffic is automatically redirected to the remaining healthy servers. This fault tolerance is critical for applications that must maintain uptime, from e-commerce platforms processing transactions to WordPress sites serving content to global audiences.

Load Balancing Algorithms

Load balancers use various algorithms to determine how traffic is distributed. Round Robin is the simplest approach, sending each new request to the next server in a rotating sequence. Weighted Round Robin assigns a weight to each server based on its capacity, directing more traffic to more powerful servers. Least Connections routes new requests to the server currently handling the fewest active connections, which is effective when request processing times vary significantly.

IP Hash uses the client's IP address to determine which server receives the request, ensuring that a specific client is consistently directed to the same server, which is important for session persistence. Least Response Time combines active connection count and server response time to select the optimal server. More advanced algorithms incorporate real-time health metrics, geographic proximity, and application-layer information to make intelligent routing decisions that maximize both performance and resource utilization.

Types of Load Balancers

Layer 4 (transport layer) load balancers make routing decisions based on TCP/UDP connection information such as IP addresses and port numbers without inspecting the actual content of the traffic. They are fast and efficient because they operate at a lower level of the network stack. Layer 7 (application layer) load balancers examine the content of HTTP requests, including headers, cookies, and URL paths, enabling more sophisticated routing decisions such as directing API traffic to one server pool and static content requests to another.

Load balancers can be deployed as hardware appliances, software solutions, or cloud-based services. Hardware load balancers like F5 BIG-IP offer high performance but are expensive and inflexible. Software load balancers such as HAProxy, Nginx, and Envoy run on commodity hardware and are highly configurable. Cloud providers offer managed load balancing services, including AWS Elastic Load Balancing, Google Cloud Load Balancing, and Azure Load Balancer, which scale automatically and integrate seamlessly with other cloud services.

Load Balancing and Security

Load balancers play an important role in infrastructure security. By distributing traffic across multiple servers, they inherently provide resilience against Distributed Denial of Service (DDoS) attacks, as the attack traffic is spread across the server pool rather than concentrated on a single point. Many load balancers include built-in DDoS mitigation capabilities that can detect and absorb abnormal traffic patterns before they affect application servers.

SSL/TLS termination at the load balancer offloads the computationally expensive encryption and decryption process from backend servers, improving their capacity to handle application logic. The load balancer can also enforce security policies, such as rejecting requests with malformed headers, blocking known malicious IP addresses, and ensuring that only healthy, properly configured servers receive traffic. Web Application Firewall (WAF) functionality is increasingly integrated into modern load balancers, providing application-layer threat detection at the traffic entry point.

Load Balancing for WordPress

Load balancing WordPress requires special consideration because WordPress stores session data and uploaded media on the local filesystem by default. To properly load balance WordPress across multiple servers, administrators must implement shared session storage using a centralized store like Redis or Memcached, configure shared or distributed media storage using a service like Amazon S3 or an NFS mount, and ensure that the database is accessible to all application servers, typically through a separate database server or managed database service.

Sticky sessions (session affinity) can be configured on the load balancer to route returning users to the same backend server, which simplifies WordPress session handling but reduces the load balancer's ability to distribute traffic evenly. A better approach is to use a stateless application architecture with externalized session storage. Object caching with Redis, combined with a page caching layer, dramatically reduces the load on each WordPress server, allowing the load-balanced cluster to handle significantly more concurrent visitors than a single server could manage.