
Company \| Products \| Solutions \| Support \| Pricing \| Downloads \| F.A.Q \| Clients \| Blog \| Contact us

Quick link products
Enterprise
Enterprise R16
Enterprise MAX
Enterprise 10G
Enterprise VA (VMware)
Enterprise EC2 (AWS)
Products matrix

Load balancing Web Servers

The entire Loadbalancer.org ENTERPRISE product range supports load balancing web servers and starts from as little as $1,495!

Load balance a wide variety of applications with Loadbalancer.org

Our product range can be deployed to load balance a wide variety of server load balancing requirements.

Load balance any TCP or UDP based protocols

All Loadbalancer.org products can be implemented to load balance any TCP or UDP based protocols.

Load Balancer - What if I have some questions?

Please contact us straight away by email or phone.
Phone: +1 866.229.8562
Email: sales@loadbalancer.org

Load balancing Web Servers

As the e-commerce industry continues to grow, more businesses rely on their Web sites to communicate with customers. A high-performance Web site that quickly and reliably delivers content gains and retains customers and is crucial to a successful and competitive e-business. Few potential customers will return to a frustratingly slow Web site if the customer experiences significant delays or failure. Thus, as part of your organization's Web infrastructure planning and implementation, you may need to seriously consider how to improve your Web site's performance.

Sharing the Load
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. Adding additional capacity as demand grows is straightforward and can be achieved by simply adding additional IIS servers to the virtual cluster.

Providing Resilience
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.

SSL & Certificates
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 (aka SSL off-loading) or on the web servers. When terminating SSL on the load balancer, it is important to consider that data is not secured between the load balancer and the backend web servers and is transmitted unencrypted.

Persistence (aka Server Affinity)
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.

Supported Load Balancing Methods
The Loadbalancer.org appliance support all major load balancing methods, with numerous modifications and customizations to suit your requirements. Below are the most common configuration methods.

Direct Routing (DR)	Network Address Translation (NAT)	Source Network Address Translation (SNAT)

The one-arm direct routing (DR) mode is the recommended mode for Loadbalancer.org installation because it's a very high performance solution with very little change to your existing infrastructure	If DR is not possible the second choice would be NAT. This is also a fairly high performance solution but it requires the implementation of a two arm infrastructure with an internal and external subnet to carry out the translation. (the same way a firewall works).	If your application requires that the load balancer handles cookie insertion then you need to use the SNAT configuration. This also has the advantage of a one arm configuration and does not require any changes to the application servers.

The entire Loadbalancer.org ENTERPRISE product range supports load balancing IIS / Apache Web Servers and starts from as little as $1,495!

Please see our full Microsoft IIS Deployment Guide for further information.