HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
oban-bg
oban
Elixir2019–2026
oban-bg / oban

oban

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

28Distinct people
36Mentions
1Explicit recommenders
4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Just curious, if you’re already in Elixir and using Postgres, why not use Oban[1]? It’s my absolute favorite background job library, and the thing I often miss most when…

mmcclure used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year36 dated mentions

Observed mentions: 2019-12-20 16:11:41 UTC to 2026-04-30 17:12:06 UTC.

02468102019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC707
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC909
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC1019
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC413
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Robust job processing in Elixir, backed by modern PostgreSQL, MySQL, and SQLite3. Reliable, observable, and loaded with enterprise grade features. Table of Contents Features Oban Pro Engines Requirements Installation Quick Getting Started Learning Community Contributing Note This README is for the unreleased main branch, please reference the official documentation on hexdocs for the latest stable release. Features Oban's primary goals are reliability, consistency and observability. Oban is a powerful and flexible library that can handle a wide range of background job use cases, and it is well-suited for systems of any size. It provides a simple and consistent API for scheduling and performing jobs, and it is built to be fault-tolerant and easy to monitor. Oban is fundamentally different from other background job processing tools because it retains job data for historic metrics and inspection. You can leave your application running indefinitely without worrying about jobs being lost or orphaned due to crashes. Advantages Over Other Tools Fewer Dependencies — If you are running a web app there is a very good chance that you're running on top of a SQL database. Running your job queue within a SQL database minimizes system dependencies and simplifies data backups. Transactional Control — Enqueue a job along with other database changes, ensuring that everything is committed or rolled back atomically. Database Backups — Jobs are stored inside of your primary database, which means they are backed up together with the data that they relate to. Advanced Features Isolated Queues — Jobs are stored in a single table but are executed in distinct queues. Each queue runs in isolation, with its own concurrency limits, ensuring that a job in a single slow queue can't back up other faster queues. Isolated Jobs — Every job runs in a dedicated process to provide fully concurrent execution, a clean environment between jobs, and efficient cleanup after the job runs. Queue Control — Queues can be started, stopped, paused, resumed and scaled independently at runtime locally or across all running nodes (even in environments like Heroku, without distributed Erlang). Resilient Queues — Failing queries won't crash the entire supervision tree, instead a backoff mechanism will safely retry them again in the future. Job Canceling — Jobs can be canceled in the middle of execution regardless of which node they are running on. This stops the job at once and flags it as cancelled. Triggered Execution — Insert triggers ensure that jobs are dispatched on all connected nodes as soon as they are inserted into the database. Unique Jobs — Duplicate work can be avoided through unique job controls. Uniqueness can be enforced at the argument, queue, worker and even sub-argument level for any period of time. Scheduled Jobs — Jobs can be scheduled at any time in the future, down to the second. Periodic (CRON) Jobs — Automatically enqueue jobs on a cron-like schedule. Duplicate jobs are never enqueued, no matter how many nodes you're running. Job Priority — Prioritize jobs within a queue to run ahead of others with ten levels of granularity. Historic Metrics — After a job is processed the row isn't deleted. Instead, the job is retained in the database to provide metrics. This allows users to inspect historic jobs and to see aggregate data at the job, queue or argument level. Node Metrics — Every queue records metrics to the database during runtime. These are used to monitor queue health across nodes and may be used for analytics. Graceful Shutdown — Queue shutdown is delayed so that slow jobs can finish executing before shutdown. When shutdown starts queues are paused and stop executing new jobs. Any jobs left running after the shutdown grace period may be rescued later. Telemetry Integration — Job life-cycle events are emitted via Telemetry integration. This enables simple logging, error reporting and health checkups without plug-ins. 🌟 Oban Pro An official set of extensions, plugins, and workers that expand what Oban is capable of is available as a licensed package. It includes features like: Smart Engine — Enables global concurrency, global rate limiting, queue partitioning, and auto insert batching for truly distributed job processing. Pro Worker — Extends workers with execution hooks, structured args, output recording, encrypted args at rest, and chained execution. Workflows — Compose jobs with arbitrary dependencies for sequential, fan-out, and fan-in execution patterns. Batches — Process related jobs while tracking overall progress across all nodes and executing optional callbacks. Dynamic Plugins — Runtime configuration of cron schedules, queues, job priorities, and automatic scaling—ideal for applications that manage jobs dynamically. Decorator — Build and insert jobs directly from regular functions without defining worker modules. Learn more about Oban Pro → Engines Oban ships with engines for PostgreSQL, MySQL, and SQLite3. Each engine supports the same core functionality, though they have differing levels of maturity and suitability for production. Requirements Oban requires: Elixir 1.15+ Erlang 24+ PostgreSQL 14.0+, MySQL 8.4+, or SQLite3 3.37.0+ Installation See the installation guide for details on installing and configuring Oban in your application. Quick Getting Started Configure queues and an Ecto repo for Oban to use: # In config/config.exs config :my_app, Oban, repo: MyApp.Repo, queues: [mailers: 20] Define a worker to process jobs in the mailers queue (see Oban.Worker): defmodule MyApp.MailerWorker do use Oban.Worker, queue: :mailers @impl Oban.Worker def perform(%Oban.Job{args: %{"email" => email} = _args}) do _ = Email.deliver(email) :ok end end Enqueue a job (see the documentation): %{email: %{to: "foo@example.com", body: "Hello from Oban!"}} |> MyApp.MailerWorker.new() |> O
Read the full README on GitHub

What Hacker News says

9 sources
oh boy. where to begin > We built a few services So you never really committed to it in the first place. Also, this complicates the deployment problem. > after a few years some of the original people that introduced it left the company Probably left for a company that actually committed to Elixir. :P > and it became very difficult to hire for In a world where everyone is remote and where 10 Elixir people apply to every job, this product must have been pretty unappealing > New hires were either people wanting to learn (so we had to spend a good bunch of resources into teaching + end up with a system built by noobs to the language) or very expensive developers with a lot of experience in erlang and elixir. "We didn't want to pay employees their worth and instead bitched about what we couldn't get without hiring those employees" (Why couldn'
Read the rest
t you hire an assortment? One experienced guy and a couple noobs?) > We also found many times missing libraries, or found libraries which are incomplete, or unmaintained or just not well documented Alright, fine. Sometimes you have to "roll your own" in this space, still. > Tooling is just terrible. The VSCode plugin is crap You should not use the word "tooling" here because VSCode is not an IDE, Elixir should not require an IDE, and moreover, Elixir should not be judged because "there is no good IDE for Elixir". "Tooling" should refer to the support libs and tools that ship with the language, all of which are excellent. > At that point you're just reinventing your crappy undocumented and untested version of delayed_job. Spotted the guy who never heard of Oban https://github.com/sorentwo/oban Benefit of the doubt: Perhaps it didn't exist yet. > Most of what you get from elixir in terms of redundancy, high availability, etc you can have that anyway from kubernetes, heroku or any PaaS This is entirely missing the point. If a bug or runtime error crashes your Ruby interpreter, you better have another one ready to go from a pool (because Rails stacks can take a while to load), and then you better not exhaust that pool! If such an error crashes Elixir, it just restarts the process, which only takes a millisecond because forking an immutable language's state is trivial compared to a mutable language's state. > Liveview I actually haven't played with it much yet so can't comment > In the end, we are back to Rails and much happier "We can underpay cheap devs again" You also repurchased entire classes of bugs that are impossible in Elixir such as: mutation bugs, monkeypatch bugs, and concurrency bugs (just forget running your test suites in parallel). Also, these are literally the hardest types of bugs to fix (nondeterministic behavior), and will likely cost you more in the long run than any differential salary you balked at (I have spent entire months debugging something in the Ruby space, you'll remember my comment once this bites you in the *** one day).
In Ask HN: Are you satisfied with Elixir or do you regret choosing Elixir?
> Tooling is just terrible. The VSCode plugin is crap, kills the CPU unless you disable features. There is no IDE from jetbrains. There is a plugin but last time I tried it, it was even worse than the VSCode plugin. I am using VSCode too and the experience is not as good as with Typescript/Javascript but is not that terrible either. I would compare it with Rust's experience, so far. > Also, I've read some comments where people mention "we don't need redis", "we don't need workers" everything is so much easier. That was our thinking at first. But then you realize on deployments you will lose your cache, or your background jobs, etc. So you have to persist them either in mnesia or in the database. At that point you're just reinventing your crappy undocumented and untested version of delayed_job. Of course you need _other_ libraries to achie
Read the rest
ve some of those things. You do not have a queue built it but there are some very good tools like Oban https://github.com/sorentwo/oban that are basically doing what Sidekiq does, just relying on the main database you are already using. There are also very good libraries for caching that rely on ETS and that simply replaces what you could do with Redis. > Most of what you get from elixir in terms of redundancy, high availability, etc you can have that anyway from kubernetes, heroku or any PaaS.... you will need more than 1 server anyway, so... This is partially true. The ability of BEAM to cluster and execute processes inside the cluster, internal communication between actors and so on are not _just_ achievable with k8s, not without a good added complexity.
In Ask HN: Are you satisfied with Elixir or do you regret choosing Elixir?
José is an enormous asset to the community and has an influence on many of the marquee projects, but it definitely isn't single-handedly done. He cares about the ecosystem and is very generous with his time and attention. Anecdotally speaking, he hasn't been hands on with Oban[1], yet he still offers advice and guidance around the project because it is in the Elixir community. 1: https://github.com/sorentwo/oban
In José Valim Reveals “Project Nx” (Numerical Elixir) [audio]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.