TechCrunch Labs: Our Experience Building And Launching An App...
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Bookmark History
Saved by 10 people (0 private), first by anonymouse user on 2008-04-09
- Steflm on 2008-04-23 - Tags application , google , paas , web20 , imported1s
- Pixelnated on 2008-04-15 - Tags techcrunch , appengine , programming , Django , Python , Google , imported
- Teximo on 2008-04-15 - Tags programming , google , googleappengine
- Hkeziah on 2008-04-14 - Tags google , app-engine
- Rohitaggarwal on 2008-04-12 - Tags no_tag
Public Sticky notes
The SDK provides a server that emulates the App Engine platform, making it possible to easily develop applications locally that will later deploy to Google’s cloud. Once we had a presentable first app coded up and tested locally, we deployed the app to Google’s server easily from the command line. This was particularly compelling; we’ve spent hours or even days deploying web apps to comparatively trivial servers.
Overall, the process from sign-up to deployment took about 4 hours, with the vast majority of that figuring out what we wanted to do and remembering how to do things like sort arrays in Python (we also spent an embarrassing 15 minutes on some poorly formatted hidden HTML fields). The rapid prototyping of the app and the ease of deployment is clearly the real power of App Engine right now. The scalability of App Engine is exciting but elusive; most apps won’t need it for a while. It’ll also be interesting to see how truly scalable it is, considering the linear scaling efforts on Amazon EC2. The redundancy and ease of deployment should be the immediate attraction for developers.
Highlighted by rohitaggarwal
Public Comment