Live chat

"We've been using load balancers from on our high traffic web application since 2004 - and never had a single failure. The hardware and software has performed flawlessly for over 10 years. It was easy to setup and has been easy to maintain. And the support has been fantastic. I have no reservations recommending this product to anyone who needs a HA load balancer solution."

Brook Davies

Logiforms Software

Load Balancing Microsoft IIS

Internet Information Server (IIS) is a high performance Web Server platform from Microsoft. For many large e-commerce web sites it’s essential to build a web farm of multiple IIS web servers. In order for these web sites to remain available IT managers will need to configure IIS server load balancing. provide hardware, virtual and cloud solutions for advanced IIS web server load balancing.

The primary function of the load balancer is to distribute inbound connection requests across multiple web servers. This allows administrators to setup multiple servers and easily share the load between them. With, adding additional capacity as demand grows is straight-forward and can be achieved by simply adding additional web servers to the virtual cluster via the intuitive web user interface.

Typically, two load balancer appliances are deployed. This ensures that a single point of failure is not introduced. A heartbeat signal between the pair is used to ensure that should the active unit fail, the passive unit takes over. Web server monitoring is also used to ensure that failed servers are removed from the cluster and client requests are only directed to functional servers.

For secure web sites & web pages, SSL is used. This ensures that data is encrypted between client and server. SSL certificates can be installed on the load balancer appliance (aka SSL offloading) or on the web servers. When terminating SSL on the load balancer, it’s also possible to enable encryption between the load balancer and the backend web servers for full end-to-end encryption (aka SSL bridging). For full scalability, generally recommends terminating SSL on your IIS web servers.

Ideally, persistence should be considered at the start of any web server project. A database is typically used to maintain session information. This information is then available to all web servers so that whenever a user connects, any previous session details can be accessed. If this structure is not in place, persistence can be implemented on the load balancer. For HTTP, this can be either based on source IP address or cookies – both ensure that repeated connections within a session are always sent to the same backend web server. The entire product range supports various methods of persistence.

The appliance support all major load balancing methods, with numerous modifications and customization’s to suit your requirements.

Surely you must have a question?