Windows NLB Vs Hardware Load Balancer for SharePoint

It’s a best practice to use Hardware load balancer rather Windows NLB for SharePoint (or any other web applications!) for the following reasons:

  1. NLB uses local resources on each server in the cluster – Which means the additional load on SharePoint servers!
  2. NLB Cannot detect service outages. It can only detect server outages by IP address. If a particular server service fails, is hung, slow, or depreciated – WNLB cannot detect the failure and will still route requests to that server.
  3. NLB doesn’t provide any specific feature or optimization such as SSL offloading, compression, Caching, Certificates management, etc.
  4. NLB is DNS Round Robin (RR) which simply forward the client hits to defined interfaces. So it leads to uneven spread of workloads across cluster nodes resulting in slow user response times and high latency for the application.
  5. Performance can degrade as more nodes are added to the cluster
  6. Adding or removing a single node can cause clients to reconnect to the WNLB cluster.
  7. It cannot provide reverse proxy services functionality.
  8. Only supports source IP address affinity/persistence.
  9. All hosts in a cluster must be located in the same subnet.
  10. NLB Cannot provide pre-authentication and Single-Sign-On functionality features which are important for SharePoint.

So, A dedicated hardware load balancer addresses these drawbacks and makes configuring and managing a load-balanced environment a whole lot easier! Use NLB ONLY if the hardware load balancer is not available.

Salaudeen Rajack

Salaudeen Rajack is a SharePoint Architect with Two decades of SharePoint Experience. He loves sharing his knowledge and experiences with the SharePoint community, through his real-world articles!

Leave a Reply