Google App Engine Review
One of the first PaaS solutions around and still one of the best


One of the first PaaS solutions around and still one of the best, Google App Engine is a solid choice to launch your next app idea. You can deploy Java, Python or Go based web apps and enjoy a variety of free and low-cost add-ons.

If you want a mostly-static website with some dynamic content, strongly consider the webapp2 framework. It is light-weight and easy to learn. With just a few lines of Python code, you can deploy an app that can serve a website, provide database backed storage, send emails and make HTTP requests. If you want to go enterprise, it is rare to find a Spring compatible hosting service for cheap, let alone free, but here it is.

One thing that App Engine can do better than any other free service is send emails. If your app needs to send emails, I would strongly consider App Engine. As if that is not enough, your app can actually receive e-mails as well. You can also send and receive instant messages using the XMPP protocol. If your users likely have a Google account, you can authenticate them and consume other Google APIs with ease.

If your website gets incredibly busy you have the option to scale up the performance of your website and pay a small fee. For example, a single massive burst to your site may cost you $0.50 –  $1.00. A constantly busy site will cost you more. You have complete control of the billing and can set quotas and alerts. Unlike the other PaaS services, pricing ramps up gradually as your traffic increases.

If your website is not very busy then there is a down-side: Your website may pause for a couple seconds the first time someone accessess a page after it has been idle for some time. In the grand scheme, this is a very minor point, but it is present. Also, signing up for App Engine requires you to authenticate your identity by receiving a text message. Once confirmed, you can deploy a website in about 30 minutes.

  • Pros: three languages, database support, excellent email sending, Google integration
  • Cons: Performance can be poor on idle websites, signup requires a text message

Checkout the 5 minute tutorial or sign up.

While Google’s App Engine has a more linear price curve as your app grows in popularity, I have to give creds to Heroku for making pricing simple and clear.

Which to choose?

  • If you want a static website that showcases your open source involvement, use Github pages.
  • If you need a static website with geographic diversity and you don’t mind paying a very low amount, or if you need to host large amounts of data (like Videos or file downloads) use Amazon’s S3 service
  • If you want to host with PHP or you want a very generous PaaS solution and can tollerate unclear vendor support, use Openshift
  • If you want Ruby on Rails support use Heroku
  • If you are OK with Python support and/or you need excellent e-mail sending capability use App Engine
  • If you just don’t know what you want then use App Engine and see if it meets your needs. If it doesn’t, by then you’ll know what you do want and can pick the right tool.
  • Read the full post on my blog.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
2 visitors found this review helpful

1 Comment

it_user4401VendorPOPULAR

You are right, I can deploy Java, Python or Go based web applications. Related to this topic, do you know which JVM languages I can use in my App Engine application?

09 June 14
Guest
Why do you like it?

Sign Up with Email