Load balancing and clustering is needed when there is a hike in traffic in a server due to daily activities or an important event from time to time. Server goes down occasionally and users find it difficult to access your website at a time when they would desperately want to peek in like declaration of a contest result or high number of subscription. To avoid these circumstances from snatching away your traffic, it is suggested that you use a load balancing and clustering service to keep the server running smooth. A very common server cluster configuration is a web server cluster or web cluster, which spreads Internet traffic over several web servers using load balancing. The result is high-availability server with increased capability and uptime.

HAProxy is an open source load balancer that functions as a fast proxy server and provides high availability for TCP and HTTP-based applications. HAProxy is available as a package in pkgsrc on any Linux based server you provision. HAProxy stands for High Availability Proxy, and is a great TCP/HTTP load balancer which is highly recommended. Basically it distributes workload (Traffic) across a set of servers (Web Farms) to maximize performance and optimize resource usage. This process helps ensure redundancy and fail-over solutions.

Layer 4 Load Balancing

Layer 4 load balancing is the most basic method of balancing traffic over a network across multiple servers. Its simplicity means lightning fast balancing with minimal hardware.
One of the best known Layer 4 load balancers is Microsoft Network Load Balancer or NLB, which is a core network load balancer software that is available for mission critical Microsoft applications including Microsoft Exchange and Microsoft OCS. Like other Layer 4 load balancer solutions it is marginally simple. Most of the layer 4 load balancers perform the following functions:

  • Load balances at a basic level and directs traffic on the basis of server response time.
  • Each server shares the same IP address
  • Least busy server responds to content demands
  • Round Robin DNS used extensively

Layer 7 Load Balancing

Layer 7 load balancing is more complex but far more efficient.
A layer 7 configuration knows exactly what protocol it is working with – HTTP, HTTPS, FTP, etc. and so it works more efficiently and intelligently thus directing specific traffic to different servers for optimum user experience.

CloudEgg layer 7 load balancers are located in separate racks and powered by separate feeds thus eliminating all single points of failures.


  • Direct specific users to different servers for appropriate and optimum customer service.
  • Manages individual services on specific servers.
  • Load balancers are powered and stored separately for increased resilience.
  • Load balancing over multiple locations, providing the perfect solution to server failures

Server requirement:

  • 2 servers minimum with one ordinary server
  • Second high configured hardware node with VT enabled processor along with 5 or more IP’s.