The WHAT - Load Balancing in simple terms
As displayed in this example image below, Load Balancing in its simplest form means having a device (load balancer) setting in front of two or more Web or Application Servers.
The Load Balancer will monitor the Servers and split the load between the Servers based on your preferences.
Why Use a Load Balancer
Regardless of how much Ram or CPU you throw at a server, there is a physical limitation to the amount of requests it can handle.
By utilizing a Load Balancer, you can spread the load amongst multiple servers (generally 2 servers will handle most scenarios).
Handle larger number of visitors or requests during "peak" traffic times
Ensure uptime for mission critical sites or applications
Another option is to have the Servers load balanced based on load.
How to get started with a Load Balanced solution
Successful implementations of a Load Balanced solution start with a free consultation with our Server Engineers. In this no pressure call, our load balancing specialist can answer any questions you have.
Real Life Solution - Large City Government Planning for 7,000 visitors per MINUTE
To serve 7,000 people per minute for a large City Government, load balancing their web-servers was a perfect fit.
Their main objectives were:
- < 4 second load time (Actual Result: < 1 second load time)
- 7,000 visitors per minute (Actual Result: 6,000 visitors per minute)
Knowing their objectives, this gave us all the needed information to successfully deploy solution that fully met their needs.
Once we had the updated version of their application from the development team, we ran new tests successfully. The final testing of the fully deployed solution was the remaining step before their official launch. The specs for the solution that would meet their performance objectives (< 4 second load time, 7,000 visitors) included:
- Load Balancer & Virtual LAN
- Windows Servers
- MS SQL Database Servers
This solution worked perfectly. Not only were we able to help them achieve their goals; we went a few steps further. Their database server was prepared for disaster, by log shipping to their secondary database server. Additionally, we helped them implement CloudFlare for CDN & Caching to turbo charge the load time.