Some of the later helper frameworks and tools for applications written for Google App Engine are: SimpleDS and Objectify - two persistence frameworks, Kotori – a JUnit runner, Apple Guice – a case study GWT application, and Engine Watch – a GAE monitoring application for Android devices.
Google App Engine was initially using Apache Tomcat as their webserver/servlet container but eventually switched to Jetty.
JRuby 1.3 is now available, bringing performance improvements and compatibility with Google AppEngine. Work on other improvements is continuing and a first version of the ruby2java compiler is now available. Also: InvokeDynamic support is making it's way into the builds for the next Java version.
In this virtual panel, InfoQ wants to find out from leading cloud experts what are the benefits brought by cloud computing as well as the constraints in using them, what is better to use, a public or a private cloud, is the cloud interoperability needed, what is the difference between providing infrastructure or a platform, and how can a client enforce regulatory compliance.
With JRuby 1.2 released, the JRuby community is working on new projects such as a new Ruby to bytecode compiler, a standalone JRuby parser and a first release of the bytecode generating DSL Bitescript. Also: JRuby works on Google App Engine's newly announced Java support.
Google has broadened their Google App Engine (GAE) support to include Java in addition to Python. However, it also imposes a number of limitations on the GAE Java applications to further Google's ability to scale and cluster them with minimal effort.