InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

JRuby Roundup: GitHub:FI, JRuby on JBoss with TorqueBox, EngineYard with JRuby Support

Posted by Werner Schuster on Jun 02, 2009

Sections
Architecture & Design,
Development,
Operations & Infrastructure
Topics
JRuby ,
Ruby ,
Deployment / Datacenter ,
Java ,
Dynamic Languages ,
Cloud Computing
Tags
JRuby ,
Deployment ,
github ,
JBoss

GitHub just announced their new commercial product GitHub:Firewall Install (or GitHub:FI):

GitHub:FI is a version of GitHub that can be installed within your own private network. This product is ideal for your company if you wish to enjoy the benefits of GitHub, but are unable to do so because of corporate restrictions or laws that prevent you from hosting your code with a third-party service.

GitHub is written in Ruby - and GitHub:FI is shipped and installed with JRuby:

The primary difference is that the FI source code is compiled and run with JRuby inside of a Jetty container instead of our normal Ruby/Mongrel stack. Beyond that, FI looks and acts just like the site you've come to know and love.

While GitHub:FI uses Jetty, another popular Java app server has entered the JRuby market: TorqueBox which is built on JBoss AS:

TorqueBox is a new kind of Ruby application platform that integrates popular technologies such as Ruby-on-Rails, while extending the footprint of Ruby applications to include support for Job Scheduling, Task Queues, SOAP Handling, and Telecom.

The Telecom support consists of VoIP features which allow to handle and send SIP messages. The SIP features build on Mobicents.
For a quick look at what makes TorqueBox tick: the source code is hosted at GitHub.

It's not just software that gets JRuby support: EngineYard will start to offer JRuby as a runtime option:

The Engine Yard decision to provide JRuby support stemmed from requests from Java-based customers and partners that wanted to leverage existing libraries and infrastructures but also deploy their applications to a Rails cloud.

A beta of the JRuby support will be available in July; attendees of JavaOne can also pop by EngineYard's booth for more infos.

Finally: Charles Nutter posted a handy list JavaOne sessions that either feature JRuby or other dynamic JVM languages.

No comments

Watch Thread Reply

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.