DEBUG MODE ON Cloudcamp Barcelona

419 views

Published on

A brief overview of the Google App Engine pros and cons.

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
419
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

DEBUG MODE ON Cloudcamp Barcelona

  1. 1. Google App Engine: The Good, the Bad and the Ugly http://www.debugmodeon.com
  2. 2. What is Google App Engine? • A platform for running webapps on top of the Google Infraestructure • BigTable for storage and persistence • APIs for authentication with google domains • Automatic scaling and load balancing • Python or Java (or any language that runs on the Java Virtual Machine: Groovy, Scala, Jython, JRuby, PHP over Quercus,...)
  3. 3. The Good: easy & cheap • Forget system administration • High availability, automatic scaling and load balancing • As cheap as free in most cases • 5.000.000 pageviews/month for free • 10GB transference/day for free
  4. 4. The Bad: some big limitations • No text search (FULLTEXT) • No threads. But you don’t need them • No sockets. URLfetch API for web services • No file storage • Strong quotas: 1000 files per application, maximum entity size 1Mb, 30 concurrent connections,...
  5. 5. The Ugly: you are in a blackbox • Vendor lock-in: propietary API with the Python runtime, less vendor lock-in in Java (applications are standard JavaEE) • Not mature enough (1yo). Still a preview release • Some problems fixed in the past appear in the future • No easy way to backup your data
  6. 6. Our conclusion Google App Engine is the best choice if your application doesn’t bother the limitations.

×