Lastly, we have Hyper‑V network load balancing, and the idea here,
this is a Windows Server service where we're implementing load
balancing in software in the operating system where we have two or
more identically configured Windows Servers with the NLB role
installed, and you form a cluster there. Again,
your advertising connectivity to that server farm on a virtual IP address
and NLB just simply allows traffic coming in on that virtual IP to be round
robin‑ed from one backend node to the next.
It's not a particularly robust or intelligent type of load balancing,
but it's been part of Windows Server for a long time, and you can't
beat the price. If you're familiar with Azure,
there are also plenty of software‑defined networking
load balancing options there as well.
They all have the same idea though. If one or even two of
these web VM machines were to go offline,
as long as we had at least one healthy node left in the server farm, the service would still be available and accessible on that virtual IP address.