Posted by arungupta
on January 29, 2008 at 6:32 AM PST
There are several reasons you may deploy JRuby-on-Rails application on
- Java EE is a long tested deployment platform and GlassFish
is Java EE 5 compliant.
- GlassFish "green" deployment model - just create a WAR and
dump it in
autodeploy directory. Typical Rails deployment requires to spawn
multiple Mongrels, front-ended by Apache and then manage them through
- Java EE and Ruby-on-Rails applications can be easily
integrated in one container. This allows to host JRuby-on-Rails
applications in organization who have already made investment in Java
- GlassFish comes with out-of-the-box clustering and
high-availability support. Rails applications can certainly benefit
- GlassFish offers database connection pooling allowing you
to reuse your database connections.
- Last, but not the least, JRuby-on-Rails can leverage the
extensive set of Java libraries.
I'm working on an article that will explain each of these in detail. In
the meanwhile here is a live success story.
(provides a public place for Sun
employees to store large media files) released their version 2.0 -
completely rewritten using JRuby-on-Rails and deployed on GlassFish.
Igor has good details is his
Here are some excerpts:
Development environment: NetBeans
GlassFish v2 UR1 ,
Deployment environment: 2 Load-balanced
Java System Application Server 9.1 U1,
He has explained the pain points and areas of improvements very
clearly. We are aware of the performance problems and already working
Let us know if you have had success with deploying
GlassFish. Read all GlassFish
success stories .
UPDATE (Feb 8):
Mediacast deployment diagram is now available