Hi Everyone
We are running Windows 2003 and 2008 servers.
We have an application that I am looking to introduce load balancing for, and know that MS offer this service using NLB. This would save cash as opposed to using a hardware loadbalancer like Cisco, but I was curious to know people's thoughts on it.
Does NLB have most, if not all, of the features of a hardware load balancer? For instance, let's say I had two nodes, nodea.domain.com and nodeb.domain.com. The load balanced name is node.domain.com (not sure what the exact terminology for this is, but the one that the clients connect to).
Let's say I want to split the load 50/50. If nodea went down, would NLB continue sending requests to nodea (as in the case of DNS round robin) or is it intelligent enough to know that it is unavailable?
Secondly, I have heard NLB can be problematic because of broadcast storms, but can't see much on the net. Does anyone have any info?
We are running Windows 2003 and 2008 servers.
We have an application that I am looking to introduce load balancing for, and know that MS offer this service using NLB. This would save cash as opposed to using a hardware loadbalancer like Cisco, but I was curious to know people's thoughts on it.
Does NLB have most, if not all, of the features of a hardware load balancer? For instance, let's say I had two nodes, nodea.domain.com and nodeb.domain.com. The load balanced name is node.domain.com (not sure what the exact terminology for this is, but the one that the clients connect to).
Let's say I want to split the load 50/50. If nodea went down, would NLB continue sending requests to nodea (as in the case of DNS round robin) or is it intelligent enough to know that it is unavailable?
Secondly, I have heard NLB can be problematic because of broadcast storms, but can't see much on the net. Does anyone have any info?