Why Weighted round-robin in Nginx? - Purpose & Use Cases

The Big Idea

What if your website could automatically send more visitors to your fastest servers without you lifting a finger?

The Scenario

Imagine you have several servers to handle web traffic, but some are faster or more powerful than others. You try to send requests one by one to each server in turn, without considering their strength.

The Problem

This simple approach means slower servers get the same load as faster ones, causing delays and unhappy users. Manually adjusting who gets what load is confusing and takes a lot of time.

The Solution

Weighted round-robin lets you assign a weight to each server, so faster servers get more requests automatically. Nginx handles this smoothly, balancing the load fairly without extra effort.

Before vs After

✗ Before

upstream backend {
    server server1.example.com;
    server server2.example.com;
    server server3.example.com;
}

✓ After

upstream backend {
    server server1.example.com weight=3;
    server server2.example.com weight=1;
    server server3.example.com weight=2;
}

What It Enables

This makes your website faster and more reliable by smartly using your servers' strengths.

Real Life Example

A popular online store uses weighted round-robin to send more customers to their powerful servers during sales, avoiding slowdowns and crashes.

Key Takeaways

Manual equal distribution ignores server capacity.

Weighted round-robin balances load based on server strength.

Nginx automates this for better performance and reliability.