Pondering Rails WAR’s
For organizations developing and deploying Rails apps in house, does the prospect of deploying Rails apps as a WAR give you that much? Consider this…
- JRuby’s performance is well below conventional Ruby (although inroads are being made)
- JRuby is yet to reach 1.0. Not all Rails features are supported
- Composing and successfully deploying a WAR is not for the faint-hearted, errors and poor documentation abound
And what say you Java shops considering adopting Rails, does this capability really effect your decision? Does it make the prospect of learning a new language and a ream of frameworks and plugins any prettier?
For those convinced of the Rails cool-aid (and why shouldn’t you be anyway?!), it’s neat seeing a Rails app run in the snug, familiar confides of Tomcat and alike - even if it does chug along a tad. It certainly brings into perspective the gains of using the JVM as a VM for other languages – those languages inherit its benefits.
March 15th, 2007 at 2:50 pm
I don’t want war files because I like the JVM, or Java at all for that matter.
I want war files because my clients have spent literally millions upon millions of dollars on a bunch of machines designed to run java, java development environments, integration tools, on java training for their support teams, etc…
I’d love to get them to switch to rails… but pride is a terrible thing; so is haven’t spent too much money on all the wrong crap.