Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

so i know for serving static elements (css, js, images, videos etc) you should use CDN since they are spread out throughout the world.

but how could i spread out by apache servers? is there an equivalent to CDN but for dynamical pages? or is it the traditional LAMP way.

if so, i guess my best option is to find an international hosting provider that hosts in different countries, so the content will be served from the country located nearest the client machine. any suggestions of such hosting providers?

or is it best practice to contact different hosting providers in different countries that do not relate to each other. what is the right way to go?

share|improve this question

1 Answer 1

up vote 1 down vote accepted

It depends on what you want to achieve. The challenge with having geographically disperse servers that generate dynamic content is the database retrieval/synchronisation.

If you had a central database server hosted in, say, America, and then you threw web servers into Australia, England, Russia and Korea, that would quite defeat the purpose of having a disperse network becuase they're all relying on back-haul to your databsase server.

You have to put your database AND your web servers together (so, 5 locations = 10 servers). But then of course you face the issue that with 5 different database servers in 5 different countries, you need to have read/write access to the database from all locations and synchronise them with as little latency as possible. This can be done, but you have to make sure that you design your database perfectly and usually needs to be built into the design of your systems from day one.

Whichever host you go with, you're going to face these difficulties. Some hosts may have a prioritied link between their own datacentres in different countries, some may not, you will need to ask them when you're doing your research.

share|improve this answer
    
but this is what large websites do right? to replicate data and have them in different locations? but if someone then in england access the machine in england, and another in korea, how do they update each others and the other servers database? i guess this is what i have to bear in mind. what is topic like this called? any books for it explaining in detail different strategies? pros and cons with each of them and real life examples? –  ajsie Apr 5 '10 at 22:55
    
Hi Ajse, you're correct, they replicate their data to the other sites. How do to this depends greatly on which database back end you've chosen. Doing it in Microsoft SQL is totally different to doing it in MySQL. There is generally a small amount of latency between the two sites, so something thats posted in Korea might not appear in England for 30 seconds or so. –  Mark Henderson Apr 5 '10 at 23:08
    
thanks for answering that quick:) is there more information about this somewhere so i could dig deeper into it and know how to deploy? its mysql server im using. –  ajsie Apr 5 '10 at 23:11
    
@ajsie, you might want to check out the following ServerFault questions: serverfault.com/questions/51576/… and serverfault.com/questions/30605/how-fast-is-mysql-replication and serverfault.com/questions/75417/… - for more, check here: google.com.au/… –  Mark Henderson Apr 5 '10 at 23:31

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.