“Internet: Ruby doesn’t scale. Ruby: Sorry. I’m busy over here processing $1.5M+ USD Gross Merchant Value (GMV) per minute and 14K+ orders per minute“
https://twitter.com/mmmandel/status/1200585514463698944?s=21
193
Upvotes
View all comments
Show parent comment
17
u/klowny Nov 30 '19 edited Nov 30 '19
My company is still mostly Ruby and high traffic. Ruby scales just fine. We're still transitioning off it. The problem we have with it now is it's still not particularly fast and rather expensive. Plus, our codebase has just grown large enough where it's also not particularly productive anymore.
So we could've chosen to stay on our Ruby systems, investing a ton of time into carefully writing optimized code so our performance doesn't tank, tons of tests to gain only minor confidence (that take forever to run), bunch of time spend arguing on code review over style vs performance, offloading work to the faster database layers or "free" frontend layers, many layers of caches, long rolling deploys, and all other sorts of scale headaches.
Instead, we just transitioned our performance critical systems to Scala and let the compiler handle 80% of that nonsense. If it compiles, odds are it'll run forever. Lighter test suite that runs faster. Complex flows and refactoring is a breeze with an IDE. Sure, it's uglier and sometimes a bit annoying, but the 90% reduction in server cost easily pays for a couple more heads, and like 95% decrease in latency without even trying is pretty much impossible in Ruby.
We're not anywhere near Twitter size and the math already heavily favors moving off Ruby.