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. On Mon, Aug 31, 2009 at 7:08 AM, Scott Olmsted<[email protected]> wrote: > > A software architect friend wrote me with a question I can't answer because > I don't do Java. I though I would see if any one has any comments on his > idea, or links to resources. > > Thanks, > > Scott > > He wrote: > > I'm thinking for the start-up that I will be working with of using an > architecture with Rails as the web site, but the back end consisting of a > cluster of various long-running services and integrations with other > financial institutions, to use java. It seems that all of the enterprise > middleware is java-based, so if you want to do something in that area, you > kinda have to use java or at least something that compiles down to java byte > code. > > The motivation would be to try to take advantage of the productivity gains > of RAILS at least for those portions of the site. > > The Ruby front end would function as a client of the business servers using > REST or some other API; or it could use the java JMS API to access the > queuing middleware, if we use jRuby. > > Do you have any thoughts on this architecture? Warnings? > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
