THL Toolbox > Developers' Zone > Google Serving Compressed Js Libraries >
Contributor(s): Mark Ferrera
Using Google App Engine as a CDN is another way to use Google's massively redundant infrastructure to speed up your site.
A list of concerns that be useful for other's consideration are below. It would also be good to know how our own servers would handle issues of traffic spikes, etc - some of the Google App issues noted on several websites I saw and noted below. Most of the following is sourced from: http://www.niallkennedy.com/blog/2008/04/google-app-engine.html
Google App Engine already failed the Techcrunch effect (see link below) and appears the platform is currently unable to handle referral traffic loads from a popular blog or news site typically associated with a product launch. The traffic spike cutoffs make me think twice about hosting anything of value on App Engine.
A few major issues:
1. Static files are limited to 1 MB. App Engine does not support partial content requests (Accept-Ranges). http://code.google.com/appengine/articles/quotas.html
2. Cron jobs and other long-life processes are not permitted.
3. Applications are not uniquely identifiable by IP address, leading to a lack of identification for external communications. Applications may suffer from bad neighbor penalties from API providers upset at another app on the service.
4. No SSL support. No IP address complicates signing, but port 443 is open for requests. You can rely on Google services (and branding) for trusted login and possibly future payments.
5. No image processing. Python Imaging Library relies on C, and is therefore not a possible App Engine module.
6. Google user accounts. Site visitors are very aware of your choice in web hosts each time they attempt to logon to your application. I feel like this flow makes your application seem less professional, but may be a reasonable trade-off. Google will store your user data and potentially mine its data for better ad targeting.