Website load balancing issue

I am wondering how the distributed traffic of a website is balanced. For example, I have a website with a single domain name (www.foo.com) and, presumably, it is configured as three web servers in the USA, EU and Asia separately. When the end user is in the USA, I want the user to access the physical US web server when he requested www.foo.com in his browser. When the end user is in the EU, I want the user to have access to the physical EU web server. And similarly for Asia. The advantage is that the end user can access the nearest server, which will give better performance.

I believe that most large and distributed websites are implemented in this way, such as Google. I wonder how this is implemented domestically? In more detail, how is the magic of finding the nearest server implemented?

+3
source share
2 answers

Here you go. The perfect article for you and me to understand how this works. Like @omar, it has something to do with DNS.

Global DNS load balancing, guide users based on their geography.

Quick info:

A special DNS server, or a module attached with DNS server, return different answer to different request based on the request (generally another DNS server, which is your DNS server of your ISP) IP geo-location :
www.yourdomain.com ---[CNMAE Record] ---> geo.yourdomain.com --- [ GSLB handdling, CNAME ]--> us.geo.yourdomain.com -- [A record] --> 68.178.110.21

Please feel free to take a look at this: http://dev.robertmao.com/2007/06/30/global-dns-load-balancing-for-free/

Some of the players that provide the service:

Amazon Route 53, Cloudlevarage, f5, zeus ..

Geo-DNS:

+2

DNS. DNS-, DNS IP-.

0

All Articles