Skip to content

Instantly share code, notes, and snippets.

@slagyr
Created July 9, 2013 22:04
Show Gist options
  • Save slagyr/5961714 to your computer and use it in GitHub Desktop.
Save slagyr/5961714 to your computer and use it in GitHub Desktop.
Frustrations with GAE
GAE made it really easy to get a scalable site up and running. I first used it while building cleancoders.com. But there were several things that irked me.
- The SDK is huge. And it was a bit challenging to integrate with the maven workflow.
- The 30 second hard limit was frustrating problem. We build measures into Gaeshi to handle this, but every once in a while, GAE would boot our app on exceptionally slow servers that couldn't serve our app on time.
- The use of Google login for administration was good and bad. At the time there was a 10 app limit, and collaborating with clients on the GAE admin site was awkward.
- The tight coupling with GAE's API and the Datastore made me uncomfortable.
- The straw that finally broke the camel's back was the blacklisted classes. We build an client app on GAE that worked fine locally, but when we pushed to GAE, it just wouldn't work because, to our surprise, java.awt is blacklisted.
Since starting cleancoders.com, I became much more familiar with Amazon's AWS. Using Boucher (https://github.com/8thlight/boucher) make things just as easy, and AWS is much more flexible. So that's my solution these days.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment