Github: https://github.com/Shopify/autotuner
It’s incredible how much Shopify is investing in Rails (& Ruby for that matter).
And I assumr the investment is paying off because otherwise they wouldn’t continue like this.
It’s incredible how much Shopify is investing in Rails (& Ruby for that matter).
And I assumr the investment is paying off because otherwise they wouldn’t continue like this.
Why would they bother switching if Shopify isn't having fundamental problems and they're the tog dog in their stack?
Writing new services in Java might help, but still doesn't solve the main issue if your Rails app is a monolith. Breaking up the monolith might be a bad decision and is also super expensive and might even eat lots of the potential performance gains.
When you stay in the well trod C Ruby path, you benefit from the hordes of others who cleared the landlines before you. With JRuby, not so.
The cost of running the system is almost never bottlenecked by the performance of the language itself, but rather the responsibilities of the system and cleanliness of the code. Plus, in the migration, you start incurring the cost of your Ruby code calling your JVM code (and vise versa; your systems are almost certainly not a DAG), which almost certainly has higher overhead than whatever speedup you'd get from running code in the JVM in the first place. And then you're sharing protobufs/thrift files/whatever between different languages and libraries of varying degrees of quality (good luck with those Ruby protobufs!).
Before you know it, writing a little tool to optimize your Ruby garbage collector sounds like a really great idea.