SaaSHub helps you find the best software and product alternatives Learn more →
Oban Alternatives
Similar projects and alternatives to oban
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
windmill
Open-source developer platform to power your entire infra and turn scripts into webhooks, workflows and UIs. Fastest workflow engine (13x vs Airflow). Open-source alternative to Retool and Temporal.
-
-
-
-
-
-
worker
High performance Node.js/PostgreSQL job queue (also suitable for getting jobs generated by PostgreSQL triggers/functions out into a different work queue)
-
-
-
-
pg_textsearch
PostgreSQL extension for BM25 relevance-ranked full-text search. Postgres OSS licensed.
-
-
Resque
Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
-
-
-
-
-
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better oban alternative or higher similarity.
oban discussion
oban reviews and mentions
Posts with mentions or reviews of oban.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2026-05-29.
-
SQLite is all you need for durable workflows
use oban and call it a day: https://oban.pro/
-
PgQue: Zero-Bloat Postgres Queue
Would love some insights into any technical difference between this and Oban Jobs https://github.com/oban-bg/oban in case you know about it.
Big fan of Postgres FM so I know you always got a nugget of insights.
-
A Graybeard Like Me Built the Fastest and Freest Postgres BM25 Text Search
I like that we get far with just the Postgres. For an Elixir world, it's a job processing queue via Oban[1] and a search engine via Torus[2] now.
[1] https://oban.pro/
- Oban: Robust job processing in Elixir, backed by PostgreSQL, SQLite3, MySQL
-
Why I'm excited about Go for agents
That's the issue with goroutines, threads, or any long running chain of processes. The tasks must be broken up into atomic chunks, and the state has to be serialized in some way. That allows failures to be retried, errors to be examined, results to be referenced later, and the whole thing to be distributed between multiple nodes.
It must in my view at least, as that's how Oban (https://github.com/oban-bg/oban) in Elixir models this kind of problem. Full disclosure, I'm an author and maintainer of the project.
It's Elixir specific, but this article emphasizes the importance of async task persistence: https://oban.pro/articles/oban-starts-where-tasks-end
- How to Run CRON Jobs in Postgres Without Extra Infrastructure
-
The One-Person Framework in Practice
Built my startup on phoenix and I can vouch that it was 100% the right decision. code is easy to modify/reason about. Performance smokes rails by a wide margin and its websocket support is simply amazing. There's a few really great libraries for it that just let you scale very efficiently without much effort.
https://github.com/elixir-nx/axon -> AI/neural networks
https://elixir-broadway.org/ -> consume streams from kafka or rabbitmq
https://oban.pro/ -> job processing
https://membrane.stream/ -> webrtc (make a video confrencing app)
- Show HN: IsMyAIDown – AI status monitor with Phoenix LiveView. Can you crash it?
-
Show HN: PgQueuer – Transform Your PostgreSQL into a Powerful Job Queue
I’ve been thinking about the potential for PostgreSQL-backed job queue libraries to share a common schema. For instance, I’m a big fan of Oban in Elixir: https://github.com/sorentwo/oban
Given that there are many Sidekiq-compatible libraries across various languages, it might be beneficial to have a similar approach for PostgreSQL-based job queues. This could allow for job processing in different languages while maintaining compatibility.
Alternatively, we could consider developing a core job queue library in Rust, with language-specific bindings. This would provide a robust, cross-language solution while leveraging the performance and safety benefits of Rust.
-
How to Use Flume in your Elixir Application
Oban, backed by PostgreSQL or SQLite, also provides a queue-based job processing system. Exq, on the other hand, is backed by Redis. It provides features similar to Flume, but without built-in rate limiting and batch processing capabilities.
-
A note from our sponsor - SaaSHub
www.saashub.com | 6 Jun 2026
Stats
Basic oban repo stats
36
3,917
8.7
8 days ago
oban-bg/oban is an open source project licensed under which is not an OSI approved license.
The primary programming language of oban is Elixir.
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com