[ Thanks to An Anonymous Reader for
this link. ]
“This series explores aspects of technology that are
shaping Java™ development now and in the future. The premise
of Java development 2.0 is that development is happening at a more
rapid pace, thanks to both a burst of innovation in the open source
world and the commoditization of hardware. You can rent or borrow
someone else’s hardware platform to host your application (largely
assembled from open source libraries, tools, and frameworks) at a
fraction of the cost of acquiring and maintaining your own
infrastructure.“The first series installment, “Hello Google App Engine,”
examined the notion of borrowing Google’s infrastructure to host
your Java application for free, but at some cost in terms of
flexibility. In subsequent articles, you learned the differences
between App Engine and Amazon’s EC2. Last month’s column (“REST up
with CouchDB and Groovy’s RESTClient”) surveyed an up-and-coming
alternative to relational databases: CouchDB. CouchDB’s lack of a
schema and its document-oriented nature might have seemed new to
you, but you already saw another schemaless datastore in action
with Google App Engine.“This article takes the series full circle, back to Google App
Engine. The open source world has already jumped on the App Engine
bandwagon, with frameworks starting to emerge that facilitate
developing applications targeted for the platform. You’ll see how
an open source project called Gaelyk is making it even easier to
build applications that leverage many of technologies the series
has covered to this point.”