Load balancing distributes incoming requests across multiple backend instances, enabling horizontal scaling while improving availability, responsiveness, and fault tolerance. section 6.3
Explain load balancing in relation to horizontal scaling:
- A load balancer acts as a reverse proxy between clients and backend servers. section 6.3
- It routes each request to an available instance according to a chosen strategy. section 6.3
- It allows additional instances or nodes to share traffic instead of concentrating load on one machine. section 6.3
- It supports high availability, even traffic distribution, fault tolerance, and improved responsiveness. section 6.3
Interview scenario
When an application outgrows one server, add backend instances and place a load balancer between clients and those instances. The balancer distributes incoming requests so the application can scale horizontally without directing all traffic to a single node. section 6.3
Table 6.4 Scaling strategies
|
Topic
|
Fundamentals
|
Applied skills
|
Advanced
|
|
Vertical vs. horizontal scaling
|
Understands that vertical scaling adds CPU/memory to a single node, while horizontal adds nodes.
|
Chooses horizontal scaling for stateless, cloud-native apps.
|
Designs for distributed state management and consistent performance under dynamic scaling.
|
|
Load balancing
|
Knows the role of load balancers (LB) in distributing traffic.
|
Implements NGINX, HAProxy, or cloud ELBs to balance traffic across instances.
|
Tunes load balancers for sticky sessions, weighted routing, failover, and cross-region balancing.
|
|
Autoscaling & elasticity
|
Understands that autoscaling adjusts resources based on load.
|
Configures autoscaling policies using metrics like CPU, memory, or queue depth.
|
Designs for elasticity across microservices with predictive scaling, cost optimization, and graceful scale-in/out mechanisms.
|
Compare foundational, applied, and advanced load-balancing skills, including implementation with NGINX, HAProxy, or cloud ELBs and advanced routing and failover concerns. section 6.3
















