« Return to Thread: JRuby on Rails - Deployment Options

RE: JRuby on Rails - Deployment Options

by JannaB :: Rate this Message:

Reply to Author | View in Thread

Some parts of this message have been removed. Learn more about Nabble's security policy.
apache (1.3.x, really!) virtualhosted to glassfish gem. BLAZING! No warring-up of the file, simple to set up, solid as can be. -Janna


From: wintermi@...
To: user@...
Date: Sun, 21 Jun 2009 22:12:46 +1000
Subject: [jruby-user] JRuby on Rails - Deployment Options

Hi,

I was wondering if anyone has done some tests with regards to different deployment options for JRuby on Rails.

Ideally open source deployment options. So far I have come up with the following, different combinations:

  • Jetty
  • Glassfish
  • JBoss
  • Apache + Tomcat
  • Apache + Jetty
  • Nginx + Tomcat
  • Nginx + Jetty

I am sure there are a lot more options available.

What do people currently have running in production and how have you found the deployment option with regards to performance and memory utilisation.

I have read various blog posts on the subject, but most seem to concentrate on how easy the deployment option is rather than how effective a solution it is.

For example, would it still be beneficial to place a HTTP server such as Apache, Nginx, etc in front of the Java servlet container, much like a standard RoR deployment option. Reading the Jetty, Glassfish and JBoss sites seem to suggest that you do not have to do this, and you will still be able to achieve the same or at least similar levels of performance, but I would have thought that it would still have been beneficial to place static objects behind a HTTP server, and then share the JRoR load across multiple Java servlet containers, so handling concurrency more effectively.

Any help, information on this would be most appreciated.

Regards
Matthew Winter


Hotmail® has ever-growing storage! Don’t worry about storage limits. Check it out.

 « Return to Thread: JRuby on Rails - Deployment Options