oban-bg/oban
Oban is a background job processing library for Elixir that manages job queues, scheduling, and execution. It provides database-agnostic support for PostgreSQL, MySQL, and SQLite, alongside an installation task to simplify setup. The system includes features for cron-based scheduling, distributed leadership, and plugin-based extensibility.
66.5
Adequate · 1 August 2026
11k
lines of production code
Elixir
primary language
1
bus factor · 198 authors in all
3
measurements over time
How it got here
2019 · Oban library introduction and test infrastructure
This period marks the introduction of the Oban job processing library, establishing its core architecture, configuration, and type specifications. The work also focused on building a robust test infrastructure to support multiple database backends, including Postgres, SQLite, and MySQL, while standardizing project metadata and development tooling.
9 changes
2020–2022 · multi-database and distributed support
This period focused on expanding Oban's compatibility with non-Postgres databases and distributed environments. New engine implementations for MySQL, SQLite, and inline testing were introduced, alongside peer and notifier backends for cluster coordination. The release also included a robust cron expression parser and deprecated legacy plugin modules in favor of a cleaner, top-level API.
9 changes
2023–2024 · multi-database and installation support
This period focused on expanding Oban's compatibility with MySQL and SQLite, including new migration modules and corresponding test coverage. The team also introduced an automated installation task to streamline setup for all supported database adapters.
8 changes
Survey your own repository
oban-bg/oban was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 1 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 9a0b729d7e — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.