37signals-jobs

You keep business logic out of Rails background jobs by creating thin ActiveJob classes that delegate execution directly to model methods, making asynchronous processing easier to test and maintain.

The _later/_now convention in Solid Queue provides deterministic async versus sync behavior by calling model methods, allowing you to test background job logic directly without complex job setups.

Yes, you can use Solid Queue for Redis-free background processing as it relies on a database-backed ActiveJob integration, providing recurring jobs and queue prioritization within Rails 8.2.

You test Solid Queue jobs in Rails 8.2 by testing the underlying model methods directly, ensuring your jobs remain thin orchestrators that delegate business logic rather than containing it themselves.

Yes, Solid Queue supports recurring jobs and queue prioritization alongside standard ActiveJob features, allowing you to handle notifications, batch processing, and external API calls natively.

You should not use thin jobs for asynchronous processing if your application architecture prevents moving business logic into ActiveRecord models, as this pattern strictly requires jobs to delegate all work.