3 ms·
> At the same time you can still run a single $20 / month server for "smaller" apps even with Rails + Sidekiq + Action Cable + Postgres + Redis all running on t
by pizza234 5y ago
> At the same time you can still run a single $20 / month server for "smaller" apps even with Rails + Sidekiq + Action Cable + Postgres + Redis all running on the same server to power your solo developed SAAS app with thousands of customers.
This is true but in a narrow sense. Rails and Ruby are inherently inefficient, both in the performance and memory profiles.
Rails is theoretically threadsafe, but not really - I've been hit by a threading issue just within the first hour of testing, and even if Rails was, the ecosystem isn't. Which means, one needs multiple processes, which requires lots of memory.
Speed isn't great, either. I can't really do apples-to-apples comparison, but I think it's realistic to state that equivalent, statically typed, applications are very significantly faster (without explicit optimizations), which requires more computing units.
- Lio 5y agoThings are changing on this front. We now have better fibres for IO bound code and ractors for thread safe CPU bound code. Personally I don’t think ractors are completely solid but I don’t think it will long until they are. I think Ruby’s future is pretty rosey compared to a few years ago. I would even say that small projects can avoid Sidekiq and Redis by using Good Job and Postgres making them even cheaper to start with.
- pizza234 5y agoRegarding the ractors, I'm a big fan - I believe true multithreading in a language with a GIL is a revolutionary change. On the other hand, I also believe that Ruby has always had a culture of single threading, so for the ecosystem to adjust (in practice, for having threadsafe libraries), it will take a very long time (if ever; I'm pessimitic and personally believe the ecosystem will never catch up, but of course, I wish all the best :)).