Solid Queue

What it does

Active Job behavior

Solid Queue relies on Active Job for retries, discarding, error handling, serialization, and delays.checked 11 Oct 2026

Active Job handling

Solid Queue relies on Active Job for retries, discarding, error handling, serialization, and delays.checked 5 Oct 2026

Dashboard integration

The README recommends Mission Control Jobs for viewing jobs and examining, retrying, or discarding failed jobs.checked 11 Oct 2026

Database support

It can use MySQL, PostgreSQL, or SQLite as its SQL database.checked 11 Oct 2026

Execution modes

Its supervisor runs in fork mode by default, with async mode available as an alternative.checked 11 Oct 2026

Job execution

Workers can run jobs using threads or fibers, and the supervisor can run workers and dispatchers in fork or async mode.checked 5 Oct 2026

Job features

It supports delayed and recurring jobs, concurrency controls, pausing queues, numeric job priorities, queue-order priorities, and bulk enqueuing.checked 11 Oct 2026

License

The repository identifies its license as MIT.checked 11 Oct 2026

Performance requirement

For highest throughput, the project recommends MySQL 8+, MariaDB 10.6+, or PostgreSQL 9.5+; SQLite is described as an option for smaller applications.checked 11 Oct 2026

Puma integration

A Puma plugin can run the Solid Queue supervisor alongside Puma, but phased restarts are not currently supported by the plugin.checked 5 Oct 2026

Purpose

Solid Queue is a database-based queuing backend for Active Job.checked 11 Oct 2026

Rails and Ruby requirements

The minimum supported versions are Rails 7.1 and Ruby 3.2, and Solid Queue is configured by default in new Rails 8 applications.checked 5 Oct 2026

Rails support

Solid Queue is configured by default in new Rails 8 applications and supports Rails 7.1 or later.checked 11 Oct 2026

Ruby requirement

The documented minimum supported Ruby version is 3.2.checked 11 Oct 2026

Scaling

It supports horizontal scaling, including running workers or dispatchers on multiple machines separate from the web server.checked 11 Oct 2026

Security

The repository's Security page does not display security policy content while signed out.checked 11 Oct 2026

Throughput limitation

For highest throughput, the project recommends MySQL 8+, MariaDB 10.6+, or PostgreSQL 9.5+; older versions can encounter lock waits with multiple workers on the same queue.checked 5 Oct 2026

Transactional behavior

A separate queue database is the default because relying on transactional integrity between app data and jobs can cause behavior changes if the backend or database setup changes.checked 5 Oct 2026