Skip to content
railsengines.com

GoodJob vs Solid Queue

GoodJob and Solid Queue both sit in operations, but they solve different parts of it.

Thin comparison — they do not replace the same product. Kept readable, left out of search.

GoodJob

Better known

A Postgres-backed Active Job backend that ships its own dashboard

No ratings yet
# Gemfile
gem "good_job"

# config/routes.rb
mount GoodJob::Engine, at: "/good_job"

What GoodJob does

GoodJob is a job backend and a dashboard in one gem, using the database you already run. Multithreaded Active Job execution backed by Postgres Cron-style recurring jobs Concurrency controls and job throttling A mounted dashboard: queued, running, finished, discarded, with retry and discard Runs inside your web process if you want zero extra infrastructure The reason this belongs in the directory: adopting it removes a Redis instance and a job-monitoring subscription at the same time.

Read the full GoodJob listing →

Why you might pick it

  • It also replaces Hosted job monitoring.

What Solid Queue does

Database-backed Active Job backend Solid Queue is a database-based queuing backend for Active Job, designed with simplicity and performance in mind. Installation Usage in development and other non-production environments Single database configuration Dashboard UI Setup Incremental adoption High performance requirements Workers, dispatchers, and scheduler 2477 stars on GitHub · MIT licensed · maintained by rails. Source: <https://github.com/rails/solid queue

Read the full Solid Queue listing →

Side by side

Rows where the two differ are marked.

GoodJob vs Solid Queue compared across category, licence and coverage
GoodJob Solid Queue
Category Operations Operations
Replaces (differs) Hosted job monitoring
License MIT MIT
GitHub stars (differs) 3000 2477
Gem (differs) good_job solid_queue
Mounts at (differs) /good_job
Member rating

What each one gets off your invoice

Both replace

Nothing unique here.

Only Solid Queue

Nothing unique here.

Questions

What is the difference between GoodJob and Solid Queue?
GoodJob and Solid Queue both sit in operations, but they solve different parts of it.
Can I mount both GoodJob and Solid Queue in the same Rails app?
Technically yes — engines mount at different paths — but they overlap, so running both usually means two sets of tables doing one job. Pick one.

Other comparisons in Operations