I'm heading to Google NY for the day for an appengine hackathon. I have a bazillion ideas banging around in my head. We'll see what I come back with. If anyone else is going to be there send me an email me or send me a tweet
View Larger Map
Wednesday, May 7, 2008
Appengine Hackathon!
- Link
Subscribe to:
Post Comments (Atom)
1 comments:
Greetings to all those of you who attended the New York hackathon!
It was a good opportunity to see what others have been thinking in terms of the possibilities on Google App Engine.
I must apologize for screwing up my demo and taking up valuable time on stage with my hopelessly flawed Windows Vista laptop! Damn you Microsoft!
Also, never, never give a demo of an app that doesn't fit on a 1024x768 pixel overhead projector screen! Oh well, at least my individual demos to the Google engineers went well!
Here's some quick take-away from the event:
1) Google seems to genuinely care about developer feedback on app. engine, so give it where you can
2) The application should improve over time, but for now has some drawbacks in terms of being able to manage your data (Some batch job processing / ETL would be nice to have)
3) App engine scalability still remains to be proven. There aren't many million-user apps yet (I don't know if there are any at all). Being Google, I'm sure they have this totally under control, but they may need to add more hardware!
4) Application quotas aren't set in stone, but you will have to prove that you really need to up the limits
a) You should have few errors reported in your logs, otherwise fix your app first before requesting quota level increases
5) There is no pricing model yet for paid-for bandwidth / cpu cycles, but it's coming (Any fees should be in line with other services like those provided by Amazon)
6) AppEngine is about 1 month old, as of this writing (publicly available).
7) Google has a GData / Python library for use with AppEngine, which means you can query a user's Contact List amongst other things.
All for now...
Post a Comment