[Be el o ge]

JRuby and Ioke on Google App Engine for Java

key topics:

• Why it actually might be interesting to let your Ruby app run with Jruby instead of MRI: threading, Unicode, performance, memory (much better garbage collection), c extensions > Java extensions, use Java code directly from Ruby
• Warbler: packages your Rails / Ruby application into a WAR ready to deploy
• How get Ruby work on AppEngine
  • Reggae > Getting around some general AppEngine problems
  • DataMapper > BigTable integration (via dm-datastore-adapter)
  • BeeU > mimic AppEngine user service
• Testing: local testing problematic, functional tests need to run on AppEngine directly

All in all I got the feeling that you shouldn’t run your production Rails application on AppEngine yet. There are to many caveats currently. It might be worth considering to move specific services of your application to AppEngine though. Especially those which could benefit most from the scaling advantages in the cloud.

The main points for getting your Rails app running on AppEngine you can read here and here.