Why load balancing distributes traffic in Nginx - Why It Works

Introduction

When many users visit a website or app, one server can get overwhelmed and slow down. Load balancing helps by spreading the visitors evenly across multiple servers so no single server gets too busy.

When your website gets more visitors than one server can handle smoothly

When you want to keep your app running even if one server stops working

When you want to improve the speed of your website by sharing the work

When you run multiple copies of the same app on different servers

When you want to avoid downtime during server maintenance

Config File - nginx.conf

nginx.conf

http {
    upstream myapp {
        server 192.168.1.101;
        server 192.168.1.102;
        server 192.168.1.103;
    }

    server {
        listen 80;

        location / {
            proxy_pass http://myapp;
        }
    }
}

This configuration creates a group of servers called myapp with three backend servers.

The proxy_pass directive sends incoming requests to this group.

Nginx will distribute the traffic among these servers to balance the load.

Commands

Check if the nginx configuration file syntax is correct before applying it.

Terminal

sudo nginx -t

Expected Output

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: configuration file /etc/nginx/nginx.conf test is successful

Reload nginx to apply the new load balancing configuration without stopping the server.

Terminal

sudo systemctl reload nginx

Expected Output

No output (command runs silently)

Send a request to the nginx server to verify it forwards traffic to one of the backend servers.

Terminal

curl -I http://localhost

Expected Output

HTTP/1.1 200 OK

Server: nginx

Date: Thu, 01 Jun 2024 12:00:00 GMT

Content-Type: text/html

Content-Length: 612

Connection: keep-alive

Key Concept

If you remember nothing else from this pattern, remember: load balancing spreads user requests across multiple servers to keep your app fast and reliable.

Common Mistakes

Not testing nginx configuration before reloading

A syntax error can stop nginx from restarting, causing downtime.

Always run 'sudo nginx -t' to check configuration syntax before reloading.

Using only one backend server in the upstream block

Load balancing won't work if there is only one server; traffic won't be distributed.

Add at least two backend servers in the upstream block to enable load balancing.

Reloading nginx without applying the new config file

Nginx will continue using the old configuration, so load balancing changes won't take effect.

Save the configuration file with correct settings before reloading nginx.

Summary

Configure nginx with an upstream block listing multiple backend servers.

Test the nginx configuration syntax with 'nginx -t' before applying changes.

Reload nginx to apply the load balancing setup without downtime.

Verify traffic is served correctly by sending requests to nginx.

Practice

1. Why does Nginx use load balancing to distribute traffic across multiple servers?

easy

A. To increase the size of the server's hard drive

B. To prevent any single server from becoming overloaded and improve response time

C. To reduce the number of servers needed

D. To make the website design look better

Solution

1. Step 1: Understand the purpose of load balancing

   Load balancing spreads incoming requests across multiple servers to avoid overloading one server.

2. Step 2: Recognize the benefit of spreading traffic

   By distributing traffic, servers handle requests faster and the service stays stable.

3. Final Answer:

   To prevent any single server from becoming overloaded and improve response time -> Option B

4. Quick Check:

   Load balancing improves speed and stability [OK]

Hint: Load balancing shares work to keep servers fast and stable [OK]

Common Mistakes:

• Thinking load balancing increases server storage
• Believing it reduces the number of servers needed
• Confusing load balancing with website design

2. Which of the following is the correct syntax to define a load balancing group in Nginx?

easy

A. server_group backend { 192.168.1.10; 192.168.1.11; }

B. loadbalance backend { server 192.168.1.10; server 192.168.1.11; }

C. upstream backend { server 192.168.1.10; server 192.168.1.11; }

D. proxy_pass backend { server 192.168.1.10; server 192.168.1.11; }

Solution

1. Step 1: Identify Nginx load balancing syntax

   Nginx uses the upstream block to define a group of servers for load balancing.

2. Step 2: Check the correct block and server entries

   The correct syntax is upstream backend { server IP; server IP; } to list servers.

3. Final Answer:

   upstream backend { server 192.168.1.10; server 192.168.1.11; } -> Option C

4. Quick Check:

   Use upstream for server groups [OK]

Hint: Remember: 'upstream' defines server groups in Nginx [OK]

Common Mistakes:

• Using 'loadbalance' instead of 'upstream'
• Writing 'server_group' which is invalid
• Misusing 'proxy_pass' inside server group

3. Given this Nginx config snippet, what happens when a client sends a request?

upstream backend {
  server 192.168.1.10;
  server 192.168.1.11;
}
server {
  location / {
    proxy_pass http://backend;
  }
}

medium

A. The request is distributed between 192.168.1.10 and 192.168.1.11

B. The request is sent to only 192.168.1.10 every time

C. The request is blocked because of missing proxy settings

D. The request is sent to 192.168.1.11 only

Solution

1. Step 1: Understand the upstream block

   The upstream backend defines two servers to share traffic.

2. Step 2: Analyze proxy_pass usage

   The proxy_pass http://backend; sends requests to the upstream group, distributing load.

3. Final Answer:

   The request is distributed between 192.168.1.10 and 192.168.1.11 -> Option A

4. Quick Check:

   Requests split across servers [OK]

Hint: proxy_pass to upstream sends requests to all servers [OK]

Common Mistakes:

• Thinking requests always go to first server
• Assuming proxy_pass blocks requests without extra config
• Believing requests go to only one fixed server

4. You configured Nginx load balancing but all traffic goes to one server only. What is the likely cause?

medium

A. The upstream block has only one server listed

B. The load balancing method is set to 'ip_hash'

C. The servers are offline

D. The proxy_pass URL does not match the upstream name

Solution

1. Step 1: Check upstream and proxy_pass names

   If proxy_pass points to a different name than the upstream block, load balancing won't work.

2. Step 2: Understand traffic routing

   Requests will not be distributed if proxy_pass does not reference the correct upstream group.

3. Final Answer:

   The proxy_pass URL does not match the upstream name -> Option D

4. Quick Check:

   proxy_pass must match upstream name [OK]

Hint: proxy_pass name must match upstream block name exactly [OK]

Common Mistakes:

• Ignoring mismatch between proxy_pass and upstream name
• Assuming offline servers cause all traffic to one server
• Confusing load balancing methods with traffic distribution issues

5. You want to ensure Nginx distributes traffic evenly but also keeps a user's requests on the same server. Which load balancing method should you use?

hard

A. ip_hash

B. least_conn

C. random

D. round_robin

Solution

1. Step 1: Understand load balancing methods

   round_robin distributes evenly but does not keep user sessions on one server.

2. Step 2: Identify method that keeps user on same server

   ip_hash uses client IP to send requests to the same server, maintaining session consistency.

3. Final Answer:

   ip_hash -> Option A

4. Quick Check:

   ip_hash keeps user on same server [OK]

Hint: Use ip_hash to stick users to one server [OK]

Common Mistakes:

• Choosing round_robin for session persistence
• Confusing least_conn with user stickiness
• Thinking random method keeps sessions consistent