Why is Ruby on Rails not scalable? It was the basis of major sites like Twitter and Groupon.
And now they’ve all moved to other platforms, because Ruby can handle modest volume but not high volume.
It is like moving off Ruby on Rails is a major milestone for a Silicon Valley project. The moment they literally hit it big.
Ruby on Rails has an excellent framework for efficiently coding a working app. What it lacks is a good way to find performance bottlenecks so you can remove them.
I heard that Ruby on Rails has poor performance.
It works great until you hit the bottleneck. That bottleneck is often in the ORM layer.
That is not always a solution.
Caching can improve the performance.
But not all data can be cached, especially on dynamic sites.
You can try fine tuning your database indices, especially eliminating unnecessary queries.
That only delays the inevitable. You get better performance for a while until the load increases to the new bottleneck level.
Then again, website errors and breakdowns will slow down user interaction, too.
You can add hardware.
You can add servers to handle the larger database and more ports to handle increased traffic. Moving transaction processing to another server takes some of the load off the app server.
Then you can scale it.
It is like adding a second or third row of tables to a restaurant and another entrance. At some point, the only solution is moving to another, bigger location, or opening a franchise.
I’ve heard of programmers say they can do anything in Ruby on Rails.
And then there’s the fact that Ruby on Rails is designed to be a web application. Too many sites get into trouble when they try to use it to handle messaging, database interactions and other stuff it is not good for.
That’ll hurt performance.
And shoddy coding hurts performance and scalability, no matter what language you are working in.