There are real advantages to what may at first seem like a straightjacket to any programmer who grew up opening sockets on a whim and writing to the file system whenever it felt good. The explicit limitations help architects create better applications that run more smoothly because they prevent overreaching the limits of the system. Many of the early adopters of the Java EE found themselves pulling out their hair when one of the automatic tools would take forever to deliver the magic that the API documentation promised. Making the limitations of the architecture apparent by writing a tightly limited API is more of a gift than a curse.
If there are no joins in the data store, then it will be easier to generate massive reports because the database table will be denormalized from its inception. If the jobs can't run that long, the architect can make living documents that let the user drill down to generate the necessary information on demand. That can be much more efficient than spending the entire night pre-computing something that won't be read by many people.
All of this adds up to a compelling tool for serious experimentation, the kind of monkeying around with the hope that it will turn quickly into some that's worth launching a hundred servers. The App Engine will scale up quickly and then stop on a dime as it follows the ebbs and flows of fortune's fickle whim automatically.
Aptana Cloud, like the Studio, is a set of Eclipse plug-ins that smooth the deployment process to Joyent's collection of servers. In one tab of Eclipse you edit your code, and in another you control how it's deployed to the server running Tomcat, MySQL, and PostgreSQL. You can also build out Web sites with Rails, Jaxer, and PHP. Python is said to be coming.
Sign up for MIS Asia eNewsletters.