Re:How We Moved From Microsoft ASP.NET to Rails and NoSQL
by dasil003 on Thursday May 20, 2010 @01:42AM
(#1363333)
I would be careful with Rails, when you plan to do some heavy data processing and/or if you need your application processes to run for a long time without being restarted.
Heavy data processing yes, but the long running process is bogus. The major memory leaks in Rails were patched up years ago. The tooling is a lot better today on the off chance that you do need to debug a memory leak, and the new breed of ruby runtimes such as Rubinius will keep memory in even tighter control.
Re:How We Moved From Microsoft ASP.NET to Rails and NoSQL
by Artemidoros on Thursday May 20, 2010 @04:57AM
(#1363562)
Being somewhat problematic for long running process is not only a function of memory leaks.
Even with the better runtimes now available, suggesting that they come close to the stability (and performance and long term memory consumption and profiling + debugging capabilities) you'll find on the big JVMs is not really helpful (JRuby being the obvious exception but even here I am sceptic).
If you want to test the world beyond MS I would recommend (apart from Rails or Django) looking into the Scala/Lift (my preferred toolset), Clojure/Compojure or JavaScript/Node.js combos (depending upon you language preferences).
I would be careful with Rails, when you plan to do some heavy data processing and/or if you need your application processes to run for a long time without being restarted.
For small, straightforward applications or prototyping the Ruby/Sinatra/MongoDB combo is also really really nice.