On Aug 31, 2009, at 8:11 AM, Scott Hodson wrote:
> > If I recall correctly, isn't this what Twitter eventually did? > Rebuilt the back-end in Java because of Rails' scaling "challenges"? > > There's always JRuby. Or he could build the front-end in with Groovy > on Grails. Lots of options here. (IIRC, the only part Twitter moved was the queueing system. ) I worked with Brett on a project where the front-end and business logic were all in Ruby, but there was a backend process in JRuby + Java accessible via REST. In this example all of our persistence was done on the Ruby side, the Java part was only there to allow us to use a specific Java library needed for integrating with the customer's system. If you want a queuing system to connect Java and Ruby systems, be careful in your selection. The STOMP adapter on ActiveMQ has been troublesome in the past, and to use JMS you will need to be running JRuby. There has been a lot of interest recently to using RabbitMQ as the queueing system, and there are Java and Ruby AMQP client libraries, but I haven't used a system like that in production. --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
