From Resque to SolidQueue - Rethinking our background jobs for modern times

From Resque to SolidQueue - Rethinking our background jobs for modern times
Andrew Markle • Philadelphia, PA • Talk

Date: July 10, 2025
Published: not published
Announced: unknown

If your Rails app has been around for a while, you might still be using Resque for background jobs. We were too—until scaling issues, missing features, and increasing maintenance costs made it clear that Resque was no longer working for us.

This year we migrated to SolidQueue, Rails’ new default job runner and haven't looked back. This talk will walk you through how we did it—what worked, what didn’t, and what we learned along the way.

Key takeaways:
• Why we left Resque
• How we migrated with minimal disruption using a parallel rollout
• Why we went through the effort to re-name all our queues so that they were SLO-based (within_1_minute) and why this matters
• Lessons learned, pitfalls to avoid, and how SolidQueue made our jobs (and jobs!) easier

If your background jobs are from a previous era, this talk will give you a practical, real-world migration playbook to modernize with SolidQueue—without breaking anything.

RailsConf 2025

Explore all talks scheduled for RailsConf 2025
+48