4 ms·
As better outlined in A Berkeley view of Cloud Computing GAE and EC2 serve a different purpose/market. Comparing the two on prototyping time is rather silly. Fo
by tybris 17y ago
As better outlined in A Berkeley view of Cloud Computing GAE and EC2 serve a different purpose/market. Comparing the two on prototyping time is rather silly. For instance, people are already building GAE alternatives running on EC2.
- jimbokun 17y agoIt seems like GAE is usable for displaying content and building a web interface, but any significant processing has to happen elsewhere. This is due to the limitations on a single request (I just read about the cron functionality, but it appears that the same restrictions are in place for cron jobs). Note that, even in the tutorial, the non trivial part (accepting text messages) is handled by an external service, and the app just stores and displays the data. So, an architecture that leverages the strengths of GAE might push the processing intensive parts onto servers outside of GAE, interfaced through a services API (most likely something "RESTful"). GAE would then handle the data storage, templating, and UI logic. Note that these web services might already exist, and GAE is a good candidate for building an interface on top of them (this is the case with the text message service in the tutorial). Does that make sense?