Network Load Balancing Solution

Network Load Balancing is a clustering technology. NLB uses a distributed algorithm to balance network traffic across a number of hosts, helping to enhance the scalability and availability of mission-critical, IP-based services, such as Web, Virtual Private Networking, etc. It also provides high availability by detecting host failures and automatically redistributing traffic to operational hosts.

Benefits of Network Load Balancing

Network Load Balancing servers (also called hosts) in a cluster communicate among themselves to provide essential benefits

Scalability

Network Load Balancing scales the performance of a server-based program, such as a Web server, by distributing its client requests across multiple servers within the cluster. As traffic increases, additional servers can be added to the cluster.

High availability

Network Load Balancing provides high availability by automatically detecting the failure of a server and repartitioning client traffic among the remaining servers within ten seconds while providing users with continuous service.

Manageability

Manage and configure multiple NLB clusters and the cluster hosts from a single computer by using NLB Manager or the Network Load Balancing (NLB) Cmdlets in Windows PowerShell.

Network Load Balancing Solution

Please contact us for a quote based on your needs.

Solution 1 - IIS ARR + Microsoft NLB + IIS

Making IIS website Highly Available using IIS ARR and Microsoft NLB. Applies to: Windows Server 2022/2019/2016, IIS 7.0 and above

Example of implementation

Configure ARR1+NLB, ARR2+NLB to be Windows Load Balancing servers, which provides high availability and scalability for the content servers. ARR is built as a module on top of IIS and is designed to make the routing decisions at layer 7 (application). NLB makes the routing decisions at layer 3.

Solution 2 - LVS/HAProxy + Keepalived + Nginx

Making Nginx website Highly Available using LVS/HAProxy and Keepalived. Applies to: CentOS 8.x/7.x, Ubuntu 20.x/18.x LTS

Example of implementation

Prepare 7 CentOS 7.x hosts and a virtual IP(VIP) address: 192.168.1.4

The load balancer will use 2 hosts, one primary and one standby

lb1 (default primary): 192.168.1.2
lb2 (default standby): 192.168.1.3

The back-end web servers powered by nginx

web servers: Web-1 Web-2 Web-3
image servers: Img-1 Img-2

Network Load Balancing FAQs

Frequently asked questions about our Network Load Balancing service

More FAQs about Network Load Balancing

Releated articles

Useful Resources about our NLB service

Network Load Balancing

In this topic, we provide you with an overview of the Network Load Balancing (NLB) feature in Windows Server 2016. You can use NLB to manage two or more servers as a single virtual cluster. NLB enhances the availability and scalability ...

Windows Clustering and High-Availability

Windows Server 2019 Failover Clustering New Features. John Marlin on May 13 2019 03:10 PM. This blog ...

Network Load Balancing Deployment Guide

Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 Network Load Balancing (NLB) is an optional component...

Build a Web Farm with IIS Servers

This scenario shows how to plan and configure a web farm with servers that run the Windows Server® 2012 operating system. The scenario is divided into two phases: a plan and design phase...

Failover Clustering in Windows Server and Azure Stack HCI?

A failover cluster is a group of independent computers that work together to increase the availability and scalability of clustered roles...

Catalyst Switches for Microsoft Network Load Balancing Configuration Example

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with ...

What is a Network Load Balancer and When Should I Use It?

Any business website depends on optimal performance and availability 24 hours a day, 7 days a week. Ensuring high performance ...