Seven gems to run background jobs. That's what 37signals was running before they said "this can't be right."
In Episode 6 of Making Software, I talked to Rosa Gutiérrez, Principal Programmer at 37signals and board member of the Rails Foundation. She built Solid Queue, the database-backed job queue that ships with Rails 8 by default, and we got into how it was built, what open source maintainership actually looks like, and why Ruby is having a moment again.
Seven gems, one problem. 37signals was running seven separate gems just to cover the edge cases Resque didn't handle natively. That became the brief for Solid Queue.
Disks got fast. Redis got optional. Solid Queue is built on the same insight as Solid Cache: modern database storage is cheap and fast enough that you don't need a separate in-memory service for a lot of production workloads.
What happens when millions of developers start using your gem. Going from internal 37signals tooling to bundled-in-Rails means your edge cases multiply overnight. Rosa walks through what that transition felt like, the good contributions, the bad ones, and the more recent arrival of agent-written PRs.
