App engine beats pony.key
by alper on Jun 09, 2010
- 967 views
Accessibility
Categories
Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 0
- Downloads
- 2
- Comments
- 0
- Embed Views
- Views on SlideShare
- 949
- Total Views
- 967
http://www.cherrypy.org/
Or huge complex websites that compose multiple apps.
Coming from a newspaper background, this is rather duh!
And for complex small, data heavy sites.
App Engine has some distinct characteristics which are cool (and some which aren’t).
While app engine itself is perfectly usable for a variety of applications.
We want to program, not configure. If we wanted to configure stuff, we would program Java.
if you don’t agree, you probably have not been using them enough
django non-rel ORM exists also seems like a silly idea, http://www.allbuttonspressed.com/projects/django-nonrel
I haven’t looked into the current django-couchdb and other libraries yet, but it would be nice if these were ready for mainline use.
‘expando Models rule’
Never having to migrate another database table again is a Good Thing.
Standardized project layout (a Good Idea)
Makes it 100x more likely that I’ll build a throwaway webservice on GAE than I will with django.
django-fabric: http://theironlion.net/archive/django-fabric-deploy-your-django-apps-easily/ looks too complex, lots of configuration
It removes the necessity to think about it. You can just use the API.
as soon as it gets serious you can just convert $ into scale, you never have to hire (or become!) a sysop to configure EC2 instances yourself
also you don’t need to backup because it’s a gridded setup, it will generally never go down (except when it does), at least it won’t go down for the more mundane of reasons
no aggregates
no DISTINCT
adding redundant data or by grouping data (remember, we don’t have JOINs)
for instance cannot query SELECT DISTINCT city FROM entries
so either walk through all your records (bad idea!)
or make a new table called Cities and only put city stuff in there
Not that hard and pretty easy to write a website in.
Domain linking in Google Applications is a fucking ghetto (even for domains you completely control).
It’s doable but it’s very much harder than it should be.
This may yield:
- better availability (SLAs and that kinda crap)
- more conservatism in development
- a bigger focus on Java because of paying customers
Which is a mixed bag.