NLB 2019
NLB 2019
The Network Load Balancing (NLB) feature distributes traffic across several
servers by using the TCP/IP networking protocol.
We can use NLB to manage two or more servers as a single virtual cluster.
The servers in an NLB cluster are called hosts, and each host runs a separate
copy of the server applications.
NLB distributes incoming client requests across the hosts in the cluster. You
can configure the load that is to be handled by each host.
You can also add hosts dynamically to the cluster to handle increased load.
NLB can also direct all traffic to a designated single host, which is called
the default host.
NLB allows all of the computers in the cluster to be addressed by the same set
of IP addresses, and it maintains a set of unique, dedicated IP addresses for each
host.
For load-balanced applications, when a host fails or goes offline, the load is
automatically redistributed among the computers that are still operating.
When it is ready, the offline computer can transparently rejoin the cluster and
regain its share of the workload, which allows the other computers in the cluster
to handle less traffic.
NLB is useful for ensuring that stateless applications, such as web servers
running Internet Information Services (IIS), are available with minimal
downtime, and that they are scalable (by adding additional servers as the load
increases).
Detect a cluster host that fails or goes offline, and then recover.
Balance the network load when hosts are added or removed.
Recover and redistribute the workload within ten seconds.
Scalability is the measure of how well a computer, service, or application can
grow to meet increasing performance demands. For NLB clusters, scalability is
the ability to incrementally add one or more systems to an existing cluster when
the overall load of the cluster exceeds its capabilities. To support scalability,
you can do the following with NLB:
Balance load requests across the NLB cluster for individual TCP/IP
services.
Support up to 32 computers in a single cluster.
Balance multiple server load requests (from the same client or from several
clients) across multiple hosts in the cluster.
Add hosts to the NLB cluster as the load increases, without causing the
cluster to fail.
Remove hosts from the cluster when the load decreases.
Enable high performance and low overhead through a fully pipelined
implementation. Pipelining allows requests to be sent to the NLB cluster
without waiting for a response to a previous request.