bensheldon/good_job

Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.

View on GitHub ↗Jump to charts ↓Open shareable report →

bensheldon/good_job has 3k+ stars and 250+ forks on GitHub, is written in Ruby, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 8th, 2026
Created on February 24th, 2020
Open Issues & Pull Requests: 113 (+0)
GitHub issues: Enabled
Number of forks: 259
Total Stargazers: 3,000 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.7 hours
Mean response time: 55.6 days
90th percentile: 201.3 days
Tracked items: 140

How this project is maintained

85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 80% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 47
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 768 days
Stale 30+ days: 44
Stale 90+ days: 37

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (5)
  • bug (3)
  • enhancement (2)
  • question (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

GoodJob is a multithreaded, Postgres-based Active Job backend for Ruby on Rails.

GoodJob solves the problem of job queue management by providing an in-process job execution system that leverages PostgreSQL as its storage layer. Rather than requiring a separate job processing service, it runs job workers as threads within the Rails application process itself, using Postgres to durably store and coordinate job state. This approach eliminates the operational complexity of managing external queue services while maintaining reliability through database transactions.

Teams should adopt GoodJob when they want to simplify their infrastructure by avoiding separate job queue services like Redis or specialized job processors. It suits Rails applications already using PostgreSQL that can tolerate in-process job execution and prefer operational simplicity over distributed job processing. The multithreaded architecture means job workers run alongside the web server in the same process, making it ideal for smaller to medium deployments where a single application instance can handle the workload.

The project maintains active development with regular commits addressing bug fixes, feature additions, and dependency updates. Pull requests receive timely review and feedback from maintainers. The codebase includes comprehensive test coverage demonstrating attention to reliability. Documentation is kept current alongside code changes, and the project responds to user-reported issues with fixes and clarifications.