torquebox for production. Anyone?

Question

I want to migrate my infrastructure to jRuby. The most complete options as I see is torquebox. Anyone can share something about it? compared to tomcat/jetty?

Answer 1

I am using TorqueBox 1.0 Release Candidate for 24x7 mission critical production solutions. It has been adopted as the platform of choice for all new development on my project, replacing a very expensive commercial ESB. Although HornetQ is not (yet) replacing our business's enterprise JMS provider, we are using HornetQ heavily to a growing collection of loosely coupled JRuby components.

In my view, TorqueBox is a superb blend of a world class application server with high-availability features built-in, a high performance messaging server (HA-JMS, HA-JNDI), and my favorite programming language.

As a bonus, my productivity has soared since working almost exclusively in JRuby.

Answer 2

We are using Torquebox 2.x with Sunspot/Solr for a number of search based websites for the NHS (UK). These sites have very high page views and caching is difficult so mostly we serve dynamic content.

I would highly recommend JRuby/Torquebox

1. Torquebox has excellent support via IRC and the Mailing list
2. Torquebox is open source, but commerically backed by Redhat
3. Torquebox makes infrastructure easy, no separate message queue, background processes out of the box etc. etc.
4. JRuby is threadsafe and fast
5. JRuby has access to all the Java libraries (we use jsoup, fly saucer for PDF generation)

Answer 3

We also use jboss AS7 (not Torquebox) with HornetQ and a mixed jruby java environment in critical projects for production. Assynchronous processes a treated in java in the background, the rest in jruby on rails (frontend stuff - user interaction) It will go live this year.