Portal Home > Knowledgebase > Articles Database > Multi located site
Multi located site
| Posted by cpq-dk, 10-14-2011, 06:38 PM |
| I've got an exciting task and need some input from others.
I must make a server setup that must be placed 3 cities in the world and will host some websites.
Site 1 Europe
Site 2 U.S.
Site 3 asia
It is thought that users of the page should go into a static page and choose which part they come from and then be turned to the site closest to them for speed's sake.
But how would you create a setup where the same pages with the same content must be available all 3 locations?
It is expected that the page gets approximately 100000 users in the first 2 months and up to one million users after 3-4 months.
|
| Posted by fabin, 10-14-2011, 07:07 PM |
| It can be done using geodns.
http://www.caraytech.com/geodns/
|
| Posted by mmichele, 10-14-2011, 07:13 PM |
| The user can be saved this task with some automagic selection on the server. Several Web Frameworks support geolocation toolkits like GeoIP or, in the scope of the next few years, native geolocation in HTML5.
There are many solutions depending on the type of traffic and your requirements. Off the bat, you can share a central database and replicate the web application on all nodes to fetch from it.
Alternatively, you can have a couple of actual web applications running, and peripheral proxies on the other servers. There's many more, but you might want to take a look at the Wikimedia infrastructure architecture, as they address a similar scenario.
If one user generates on average 60 page visits, that's 200k pages a day, or 2 pages/sec. You can easily cope with this with a much lesser level of redundancy...
|
| Posted by mmichele, 10-14-2011, 07:16 PM |
| I recommend against geolocation at the DNS level especially for web applications, as the resolver is often not the client, and not representative for it. The google DNS and OpenDNS are common examples for this.
|
| Posted by cpq-dk, 10-15-2011, 03:35 AM |
| Hi.
Thanks for the answers.
It is with GeoDNS is a secondary problem.
The primary goal is to find a solution on how we take care of the speed of page views.
Therefore we must have servers on 2 maybe 3 locations, not because there is different content or language.
But only because that between the 3 sites is not very much line, eg Are there between some countries in Asia and Scandinavia from 1 to 1.5 mbit therefore we will have a setup in asia and europe and eventually one in the U.S. .
It must then synchronize the data continuously appear on the page, ie continuous synchronization.
The big question then is how you do it?
Cluster?
Third party software?
a hosting controller interface?
Or something else entirely?
|
Add to Favourites 
Print this Article
Also Read
