Persistent session control maintains client session on the same web server for the duration of the session.
Distributes requests to servers based on real-time availability and load.
Automatic load re-distribution when servers are added or removed.
.Net Framework Remoting load balancing. Single Internet Information Server (IIS) management point for all servers.
Single content repository and content propagation.
Virtual Web Servers across single or multiple IP addresses.
May be combined with MS SQL database failover cluster for total front/back end solution.
It seems like Helm 4 might have some kind of load balancing built in. I am going to have to test Helm 4 out as it looks like some nice improvements for things like this.
You can use apache + mod_proxy or nginx, then any proxy server like squid or oops.
There's also support for load balancing in Cisco roaters for http traffic.
I haven't used Helm, do you mean it's used for managing clusters of servers?
Helm manages clusters of servers, but I have no idea how in depth it goes with loadbalancing. I am guessing it probably doesnt monitor servers and give a full solution, but it might be handy for a simple cost effective solution.
What's the largest site you've had to deal with? Have you had any customers you've had to move off a shared server to a quieter one or one of it's own?
We host a few portals which have a large forums and need to be on a lower populated server. We have also set up a few sites in the past across 2 or 3 servers to distribute load due to them showing up in the news or on TV.