Google app engine & CDN

Question

When using Google app engine is there any benefit to use a CDN if i wanted my file resources as closer to users?

Answer 1

Certainly. Although App Engine may cache your static content close to users, it doesn't guarantee it will do so, and it won't cache your dynamic content for you. Using a CDN is as viable an option with App Engine as it is with any other platform.

Answer 2

Now you can also dynamically cache static assets (or the whole website) with Google App Engine and this open source Python script

And, of course, if you have budget and/or pretty big requirements, then go Akamai & co.

Answer 3

You can try a tool like just ping to see the latency between many locations and the Google App Engine (which is also on different geographical locations). Might turn out a CDN is not needed for your audience.

Answer 4

Well, it is all about your budget, geography and profiling. Google app engine is free, and if properly configured it serves your content very nicely to various locations around the world. Many people actually use the app engine as a CDN! (see here, here and here)

Here is a blog post comparing the performance of the app-engine, a commercial CDN and no CDN at all for hosting a static 1MB zipped file

Try this free service (from a CDN...) to see how your app engine application performs. Here is another test site I've used

So, depending on where your site is geographically located, where your users are located and what your needs are, you need to profile the performance of the app engine and see if it is good enough. Will you get better performance from a commercial CDN? Most likely. But do you need it?