Google App Engine as your own Content Delivery Network
Posted on: Saturday, December 6th, 2008 at 3:45 pm
24 Ways has an excellent article on using Google App Engine as your own Content Delivery Network, showing you how easy it is to set one up.
A CDN is a network of servers around the world to serve content from your site from the nearest physical location. All the large sites (Yahoo, Google, Amazon, etc) use them.
After reading the above post, I was also curious to find out how if Google App Engine helps in the following:
- Compression
- Expires headers and versioning
A comment in the original post implies compression is on by default, which is what I’d expect.
Using far future expires headers can be a great performance boost for your site, and is easy to apply to assets such as images, CSS, and JavaScript files.
At the same time, if you change such a file you want to be sure your repeat visitors will not see the old one because it was cached far into the future.
So, with a simple URL Rewrite Rule we can make things like /css/version-1/site.css point to /css/site.css.
If you update site.css, you can change the version number. Browsers will not have a file from this new path in their cache so will download it and cache it into the future again.
Is it possible to do this with Google App Engine? It looks promising…
If I can find a spare moment, I may try this out on this site (which, admittedly doesn’t get that much traffic to make it worth bothering about!) — and then I’ll try it on a site that takes up most of my spare time, which gets a LOT of traffic, where it would actually be worth doing!












On December 16th, 2008 at 4:32 pm Brad Jones said :
On December 16th, 2008 at 4:33 pm Brad Jones said :
On December 21st, 2008 at 12:50 am Anup Shah said :