oban-bg/oban
Oban is a background job processing library for Elixir that manages asynchronous task execution, scheduling, and reliability. It provides a plugin-based architecture supporting multiple database backends (PostgreSQL, MySQL, SQLite) and includes features for cron scheduling, peer leadership, and job lifecycle management. The system also offers tooling for automated installation, performance benchmarking, and comprehensive testing across various environments.
66.5
Adequate · 5 August 2026
11k
lines of production code
Elixir
primary language
1
bus factor · 198 authors in all
4
measurements over time
How it got here
2019 · Oban v2.23 architectural overhaul
This period focused on the Oban v2.23 release, introducing a plugin-based architecture with distinct modules for backoff, cron scheduling, and job engines. The update also standardized test infrastructure for multiple database backends and centralized configuration, while modernizing the build environment and documentation.
9 changes
2020–2022 · multi-database and distributed coordination support
This period focused on expanding Oban's compatibility with MySQL and SQLite3 backends alongside PostgreSQL, while introducing a new benchmarking framework for performance testing. It also added robust distributed coordination features, including peer-based leader election and scalable notifiers, alongside a comprehensive cron expression parser for scheduling.
9 changes
2023–2024 · multi-database support and installation automation
This period focused on expanding Oban's compatibility with MySQL and SQLite by introducing new migration scripts and test coverage for all three supported databases. The work also included updating the PostgreSQL schema with new states and fields, while simultaneously introducing an automated installation task to streamline setup across different repository types.
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 5 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 8b3f010644 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.