Requests are evenly distributed across all upstream servers based on the user‑defined hashed key value. The optional consistent parameter to the hash directive enables ketama consistent‑hash load balancing. For example, the following configuration defines a group named backend and consists of three server configurations (which may resolve in more than three actual servers): Servers in the group are configured using the server directive (not to be confused with the server block that defines a virtual server running on NGINX). The directive is placed in the http context. To start using NGINX Plus or NGINX Open Source to load balance HTTP traffic to a group of servers, first you need to define the group with the upstream directive. Proxying HTTP Traffic to a Group of Servers NGINX and NGINX Plus can be used in different deployment scenarios as a very efficient HTTP load balancer.

Watch the NGINX Plus for Load Balancing and Scaling webinar on demand for a deep dive on techniques that NGINX users employ to build large‑scale, highly available web services.

Load balancing across multiple application instances is a commonly used technique for optimizing resource utilization, maximizing throughput, reducing latency, and ensuring fault‑tolerant configurations. Load balance HTTP traffic across web or application server groups, with several algorithms and advanced features like slow-start and session persistence.

Ipv6 compressing rules