On Nov 27, 2007 6:54 AM, Zed A. Shaw <[EMAIL PROTECTED]> wrote: > "Alexey Verkhovsky" <[EMAIL PROTECTED]> wrote: >> In the right kind of circumstances (Java/Oracle-dominated IT shop), >> I would consider using the same setup for a normal project. > Way to go. Gotta blow the big guys to get ahead eh?
Duh... get off your high horse, will ya? "Java/Oracle-dominated IT shop" => "Oracle is already there". "I would consider using the same setup for a normal project" => "it actually works". Commercial close-sourced middleware is a Bad Thing (TM), but it helps to know what works and what doesn't. JRuby/Rails on OAS does. It also has a couple of particularly useful features: in-memory session clustering that doesn't have a single point of failure, and ESI caching. > but also SQLServer is known for being yet another of those databases that > only a grand expert could ever speed up. I've heard the same thing about it, but it doesn't match my experience. >> This reminds me... I sometimes wonder if JRuby may be much faster than MRI on Windows. :) > Actually, it is, since it runs about the same speed everywhere. If that is true, it has interesting implications for the original poster. As in "if you find out that FreeTDS/ODBC is the bottleneck, try running your app under JRuby on Windows". -- Alexey Verkhovsky CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] RubyWorks [http://rubyworks.thoughtworks.com] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
