It's worth thinking a bit about the long-term plan when your hairdresser chats away about a brilliant Web application while cutting your hair. Some whispers I've heard suggest that Google might just steal your application, perhaps copying it. I'm not sure why hosting it with Google would make it any easier for them, but maybe forcing you to map it onto their architecture might help a bit.
There are any number of competitors. Amazon has its own cloud, but it takes a very different approach, giving the user an empty Linux shell. That may offer plenty of freedom, but it offers none of the handholding. It will probably take you longer to install a JVM on Amazon's Elastic Compute Cloud than to spin up a three-page Web site with Google's App Engine. But Amazon's SimpleDB also offers a richer API, including real Web services for REST and SOAP queries.
The biggest competitors may be the old-school Web hosting programs that let you share a server for a few bucks a month. They may not scale automatically, but they give you plenty of control and an older, more established type of user agreement. And while they may not be as magic as Amazon, they have a number of tools for migrating customers to bigger boxes. The last time I asked my shared hosting service to move to a new server with a different version of MySQL, it was done in an hour or two. That's not automatic, but it only took an e-mail message.
Work in progress
It is almost unfair to review the Google App Engine when it is just a beta operation, but Google has a habit of leaving some
tools in beta form for a long time. There are a number of places where the documentation and the code suggest that Google
will add more functionality pretty soon. The basic framework and the database are both quite nice, although limited. I can
imagine Google adding better automatic features for generating the CRUD (Create, Update, Delete) routines common in these
applications. Integration with Google's Wallet might also be quite useful, although it's bound to be complicated by the banking
system. Some people have already experimented with mapping the Google Web Toolkit to the system, even though that's written
in Java and translated into JavaScript.
Google might also provide some good tools that allow the different hosted applications to share user information, essentially allowing a user to move their preferences and some of their data to other applications. This kind of inter-application linking could be pretty cool.
Time will tell what Google delivers. In the meantime, this is a good sandbox for playing with simple database applications. There's a very good reason why the beta version has a waiting list.
Related articles
• Analysis: Do new Web tools spell doom for the browser?
The Web is evolving into a full-fledged app-delivery platform, calling into question the browser's ability to fulfill the
needs of today's rich Internet apps
• Special report: Rich Web development tools bring bling to the browser
• The Test Center guide to rich Web app dev tools
Frameworks for rich Internet applications can be lightweight or heavyweight, open or closed, and almost anything in between
• Analysis: AIR gets rich apps right
Adobe's AIR is safe, fast, versatile, and open, and it will be the standard platform for rich Internet applications
• Hands on: Adventures in lightweight Internet app development
Follow InfoWorld's first steps in lightweight app development for emerging mobile devices and desktop widgets
• Review: Adobe breathes fresh AIR into RIA
Adobe's rich Internet application toolkit lifts Flash and AJAX out of the browser and onto the desktop
• Review: Microsoft Silverlight rivals Flash, AJAX
Redmond's new rich Internet application boasts strong development tools, a small browser footprint, and cross-platform support
• Review: Curl 6.0 enrichens the rich Internet toolkit
Latest release is highlighted by easier customization, more sophisticated effects, AJAX interoperability, and a native-looking
Mac port
• Review: WaveMaker’s point-and-click Java
WaveMaker Visual Ajax Studio and Rapid Deployment Framework make a fast and simple facade for Hibernate and Tomcat
• Review: Refining the art of enterprise Web apps
JackBe Presto and Nexaweb Enterprise Web 2.0 Suite converge on a powerful and productive model for server-side mashups supporting
AJAX clients
• Review: Top AJAX tools deliver rich GUI goodness
Backbase, Bindows, JackBe, and Tibco General Interface bring fat features to enterprise Web clients
• Review: Inside open source AJAX toolkits
Dojo, Ext, Google Web Toolkit, jQuery, MooTools, Prototype, and Yahoo User Interface perform amazing tricks with JavaScript;
we explore what makes each tick to help you determine which one to pick
• Blog: Neil McAllister | Fatal Exception
• Blog: Martin Heller | Strategic Developer
• Blog: Tom Yager | Ahead of the Curve
Talkback
E-mail
Printer Friendly
Reprints



