oban-bg/oban

💎 Robust job processing in Elixir, backed by modern PostgreSQL, SQLite3, and MySQL

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

Summary Information

Updated 37 minutes ago
Added to GitGenius on September 17th, 2026
Created on February 25th, 2019
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 370
Total Stargazers: 3,974 (+0)
Total Subscribers: 39 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.5 hours
Mean response time: 5.1 days
90th percentile: 2.8 days
Tracked items: 146

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 98% of issues opened in the past year have since been closed. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 654 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • kind:bug (80)
  • area:oss (70)
  • area:pro (53)
  • closed:invalid (24)
  • kind:enhancement (23)
  • kind:documentation (11)
  • note:discussion (10)
  • closed:wontfix (8)

Detailed Description

Oban is a job queue and background job processor for Elixir applications that stores jobs in PostgreSQL, MySQL, or SQLite3 databases.

The tool solves the problem of reliable background job processing by leveraging your existing SQL database as the job store rather than introducing a separate message broker. This approach eliminates an external dependency, enables transactional guarantees so jobs can be enqueued atomically with other database changes, and ensures jobs are backed up alongside your application data. Jobs are retained indefinitely for historical metrics and inspection, preventing data loss even if the application crashes. Each job runs in an isolated process for concurrent execution and clean isolation between tasks.

Oban suits any Elixir application that already runs on a SQL database and needs reliable job processing without additional infrastructure. It is particularly valuable for systems where job data retention and auditability matter, where transactional consistency between jobs and application state is required, or where minimizing external dependencies is a priority. The tool provides isolated queues that can be controlled independently at runtime, including across multiple nodes, and supports pausing, resuming, and scaling queues without restarting the application.

The maintainers respond to issues and pull requests within a day. Work in the issue tracker centers on bug fixes and activity across both the open-source and commercial product offerings.