4 ms·
Well, Rails does not have a good track record with scaling. Memory requirements if nothing else will be a big hurdle to come by regardless if you have SOA, in m
by StreamBright 8y ago
Well, Rails does not have a good track record with scaling. Memory requirements if nothing else will be a big hurdle to come by regardless if you have SOA, in my experience.
Back in the day not many organizations survived on Ruby/Rails and many of them moved over to Erlang or Java just to deal with resource issues.
https://blog.chef.io/2013/02/15/the-making-of-erchef-the-chef-11-server/ https://blog.chef.io/2013/02/15/the-making-of-erchef-the-che...
Not sure what is up with Ruby nowadays. JRuby was always an interesting option though.
- pdimitar 8y agoI'm not an authoritative source by any stretch but my anecdotal evidence shows many former colleagues getting a Rails fatigue of sorts and moving to other languages. I personally moved on to Elixir but no small amount went back to Python and PHP and some got to JS, Haskell, even OCaml and Rust and Go. It's really not productive when even minor version bumps of Rails back in the days of v3.2 all the way to v4.2 were a nightmare to execute, often impossible. You were stuck with a ton of quirks for years, likely all the way to your next job. Rails was productive, but only compared to a ton of other lame half-frameworks at the time. Nowadays it isn't special by any measure. --- So TL;DR: it doesn't really matter what Ruby or Rails are up to these days. Many people have moved on, the free lunch is over and the hype is gone. Which is a good thing: hype more often than not kills technology and doesn't enable it.
- StreamBright 8y agoYeah I have seen exactly the same.