Google launched their EC2 competitor, Appengine yesterday, and all hell broke loose. And in about 24 hours, the 10,000 accounts were used up. Currently it is tied to only working with python, and Django 0.96.1 works out of the box.
The Good
- Python powered. Django works out of the box.
- No sysadmining chores.
- Promise of infinite scalability with no configuration. (Ah!)
- Free for now.
The Bad
- Python powered, if you want to use ruby/java/php, sorry you are out of luck.
- Your code is tied to Google. You might be able to reuse most of your code, but the DB/ORM sepcific code, ah you are out of luck. And if you are building database backed websites, well most of your most complex code talk to ORM.
- Too magical. Explicit is better than implicit. On the dev server I do not know where my data is stored. If I change the data model, the changed models are available immediately. But well, how do you do it?
- Free for now, and no way to pay for when your usage out grows the free quota limits.
Related posts:
- Using Appengine with Django, why it is pretty much unusable
- Two Django+Appengine Tutorials
- New tutorial – Building a search engine with Appengine and Yahoo
- Develop Twitter API application in django and deploy on Google App Engine
- Parable of the single sheep – Or How Google is destroying the internet, and nobody seems to know.
{ 1 trackback }
{ 2 comments… read them below or add one }
On dev server data is stored in /tmp folder
In my understanding 10k accounts were signed up for in about an hour. Not 24 hours.