Autotuner: How to speed up your Rails app
railsatscale.com
Autotuner: How to speed up your Rails app
1–10 of 68 posts
Re: Autotuner: How to speed up your Rails app
#2Github: 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.
Re: Autotuner: How to speed up your Rails app
#3Github: 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.
I wonder what the break even point would be to just have switched to use JVM.
Re: Autotuner: How to speed up your Rails app
#4Github: 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.
I wonder what the break even point would be to just have switched to use JVM.
The problem is the "just switching" typically means a full rewrite and has a ton of logistic challenges. Are you gonna higher an entire second team? What happens to feature work on the current system? If you keep going full-throttle on features, you'll never catch up. If you stop developing features for a prolonged time, you are putting your entire business at risk.
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.
Re: Autotuner: How to speed up your Rails app
#5Earlier quoted context omitted.
I wonder what the break even point would be to just have switched to use JVM.
The problem is the "just switching" typically means a full rewrite and has a ton of logistic challenges. Are you gonna higher an entire second team? What happens to feature work on the current system? If you keep going full-throttle on features, you'll never catch up. If you stop developing features for a prolonged time, you are putting your entire business at risk. Writing new services in Java might help, but still…
Rails on JRuby was a tenable proposition last I looked. Been a while though.
Re: Autotuner: How to speed up your Rails app
#6Github: 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.
I think it's also a by-product of the CEO starting the company in Rails, and now having top engineers being part of Ruby core team or Rails core team. To a certain degree they'r steering the Ruby/Rails ship technically.
Why would they bother switching if Shopify isn't having fundamental problems and they're the tog dog in their stack?
Re: Autotuner: How to speed up your Rails app
#7I love to see how active and vibrant the Rails community is. I used to be concerned about the viability of building new companies in Rails, since the ruby share of languages is so low these days. Based on the still-healthy community and the ridiculous productivity level that a developer can have with Rails 7+ (turbo, morph, stimulus) I still think its a fantastic stack to build a company with.
Re: Autotuner: How to speed up your Rails app
#8Github: 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.
I wonder what the break even point would be to just have switched to use JVM.
To save VM instance costs (not disks)? Probably never.
Re: Autotuner: How to speed up your Rails app
#9Earlier quoted context omitted.
The problem is the "just switching" typically means a full rewrite and has a ton of logistic challenges. Are you gonna higher an entire second team? What happens to feature work on the current system? If you keep going full-throttle on features, you'll never catch up. If you stop developing features for a prolonged time, you are putting your entire business at risk. Writing new services in Java might help, but still…
Rails on JRuby was a tenable proposition last I looked. Been a while though.
JRuby is far behind CRuby, so there are a lot of gems that you can't use, also there are not too many companies investing in JRuby itself, IMHO CRuby it's a safer bet.
Re: Autotuner: How to speed up your Rails app
#10I love to see how active and vibrant the Rails community is. I used to be concerned about the viability of building new companies in Rails, since the ruby share of languages is so low these days. Based on the still-healthy community and the ridiculous productivity level that a developer can have with Rails 7+ (turbo, morph, stimulus) I still think its a fantastic stack to build a company with.
From personal experience, I also appreciate that it's one of the easier stacks to keep updated with the latest and greatest. I've upgraded projects from sprocket-backed asset pipelines to bun in a couple days time, and the new tooling you get with modern rails really make upgrading worth it.
Last year I started a new project[1] for a member management platform and really fell in love with the new jsbundling pipeline paired with stimulus, it feels like I've rekindled my passion that led me into programming initially; the ability to hack & prototype with rails is pretty unmatched (though it's worth mentioning Django holds a special place in my heart as well)