Q29udGVudCBEZWxpdmVyeSBOZXR3b3JrcyAoQ0ROKSDigJMgYSBjb21wcmVoZW5zaXZlIGxpc3Qg b2YgcHJvdmlkZXJz

We build web applications…and there are plenty of them around. Now, if we hit the jackpot and our application becomes very popular, traffic goes up, and our servers are brought down by the hordes of people coming to our website. What do we do in that situation?

Of course, I am not talking here about the kind of traffic Digg, Yahoo Buzz or other social media sites can bring to a website, which is temporary overnight traffic, or a website which uses cloud computing like Amazon EC2 service, MediaTemple Grid Service or Mosso Hosting Cloud service.

I am talking about traffic that consistently increases over time as the service achieves success. Google.com, Yahoo.com, Myspace.com, Facebook.com, Plentyoffish.com, Linkedin.com, Youtube.com and others are examples of services which have constant high traffic.

Knowing that users want speed from their applications, these services will always use a Content Delivery Network (CDN) to deliver that speed.

What is a Content Delivery Network?

A Content Delivery Network (CDN) is a collection of web servers distributed across multiple locations to deliver content more efficiently to users. The server selected for delivering content to a specific user is typically based on a measure of network proximity. For example, the server with the fewest network hops or the server with the quickest response time is chosen. This will help scaling a web application by taking a part of the load from the service servers.

Read the entire article about Content Delivery Networks (CDN)  list of providers at MyTestBox.com - web software reviews, news, tips & tricks.