Railsatscale iconRailsatscaleSep 16, 2026 ~1 min source read

Ractor-age Rails: A How-To Guide

In our last post on Ractors, Edouard demonstrated the potential benefits of using Ractors in a Rails application. He also explained how our team has been working towards making Rails and its dependencies Ractor-friendly.

Ractor-age Rails: A How-To Guide

Share this story

Send the public story page.

Useful takeaways from this story.

In our last post on Ractors, Edouard demonstrated the potential benefits of using Ractors in a Rails application.

He also explained how our team has been working towards making Rails and its dependencies Ractor-friendly.

While we've been able to get smaller applications running on Ractors, we still have a long way to go to unlock larger applications, which use more features of Rails and many more gems.

Building the complete brief

The page is ready to read now. The fuller skim-friendly version will appear here automatically.

The useful part

In our last post on Ractors, Edouard demonstrated the potential benefits of using Ractors in a Rails application. He also explained how our team has been working towards making Rails and its dependencies Ractor-friendly. While we've been able to get smaller applications running on Ractors, we still have a long way to go to unlock larger applications, which use more features of Rails and many more gems.

How it works

  • However, we have reached a good point where we can start to talk about the process itself.
  • In this post, I want to discuss some of the patterns we've used to refactor code to work with Ractors.

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app