Load Balancing has been around for many years. When most people think about Load Balancing, they think of an appliance, such as those from Cisco, F5, Citrix, Barracuda and others. These application-neutral devices present a “virtual server” IP address and service (such as HTTP) to the outside world and when users attempt to connect, it forwards the connection to the most appropriate real server doing bi-directional network address translation (NAT) in order to increase application availability.
Figure 1: Traditional network-based load balancing diagram
Global Cloud Load Balancing uses the same basic principle, except on a significantly larger scale. While the fundamental goal of spreading traffic across a range of servers still exists, Total Uptime Cloud Load Balancing takes it to the next level. We can’t deny that there is a need for load balancing within the datacenter, but today there is an even greater need to extend the benefits of load balancing to a global audience, routing users and traffic to the nearest datacenter that can deliver the levels of application performance and availability they require.
Figure 2: Global load balancing diagram
** As shown in the diagram above, it is possible to direct users from APAC to one data center (perhaps closest to the users in that region), users from the USA to another, users from the EU to another etc. We offer a custom add-on for $49/month (for any plan) that upgrades our interface to allow regional control. By default, the interface allows you to manage a single, global configuration (e.g. all users go to data center A until it goes down, then route to data center B. Or, all users load balance between data center A and B and if one goes down, it is taken out. These are only two examples of dozens of possibilities). Ask your account manager for further information about this GEO routing capability.
For more information, visit our Cloud Load Balancing Service section.