[pdimitar]

...Rewrite in almost anything else and you'll have fast code. :)

It's quite amazing the lengths the companies will go to just to avoid changing their status quo. But for them it makes sense.

---

EDIT: Downvoters, calm down. Ruby on Rails is objectively quite a slow framework and this is proven in many public benchmarks (Techempower included). And Ruby isn't the fastest among the dynamic languages either.

Less cargo culting and more facts, please.

[BubRoss]

Stuff like this always confuses me. It's like asking how to exercise without sweating. I would think the first sign of performance problems would mean some profiling and some porting of sections to a native language. Instead some companies go down a crazy rabbit hole instead of just making some shared libraries.

[pdimitar]

I thought the same as you but then I realized that the investment in a tech stack is basically done only once and almost never revisited.

Then people go on all sorts of crazy journeys to justify their investments in pain and burned money.

Even though I get downvoted at places in this thread (and upvoted generously on others), I will never tell to people "you should always just rewrite to Elixir". Meh. If your app works fine, have it be in COBOL or PL/1 if that helps you do your job better.

But as you said, when your app/hosting starts struggling you should start rethinking your choices if all the lower-hanging fruit has been already collected.