onkara

onkara

I am trying to wrap my head around the difference between Oban & RabbitMQ i.e. when does it make sense to use Oban vs RabbitMQ?

I know RabbitMQ is one extra component in your infrastructure requiring special config, monitoring etc so from that perspective Oban is easier to setup/monitor. But in terms of support for specific use cases or features which one would you choose and why?

Showing Posts 1 to 10

kokolegorille

kokolegorille

They don’t really compete in the same space…

Oban is kinda job scheduler, backed by database.
RabbitMQ is kinda Enterprise Bus, where You submit and listen to events.

onkara

onkara OP

But could Oban be used for submitting and listening for events like RabbitMQ? and conversely can RabbitMQ be used as job scheduler?

It seems RabbitMQ will be well suited when integrating 2 or more applications through a common bus using events, right?

kokolegorille

kokolegorille

Not really, You need a rabbitmq client. You use Oban to start a job each night for example.

Right

onkara

onkara OP

In terms of performance at what point in time does Oban/Postgres show its limitations to warrant using RabbitMQ?

kokolegorille

kokolegorille

Oban is not RabbitMQ, I don’t see one replacing the other.

sorentwo

sorentwo

Oban Core Team

RabbitMQ is purely a message broker, which is suitable for sending persistent messages between nodes. It doesn’t handle scheduling, retries, concurrency, testing concerns, or any of the other features Oban provides. To get some of those features you’ll need to use a library like Broadway, but it still won’t handle errors/retries/schedules/discards or provide the ability to query your data.

Regarding the performance, Oban can easily process 1-10k jobs per-queue per-node, depending on your concurrency levels.

onkara

onkara OP

in what unit of time?

sorentwo

sorentwo

Oban Core Team

That is per second, as measured on my local machine.

onkara

onkara OP

@sorentwo Since you are the author of Oban, is it possible for you to share benchmarks since 1-10 is pretty wide range and I need to justify to my superiors in a Forture 200 company the choice of using Oban vs RabbitMQ, which I understand is not the right choice for job scheduling and requires jumping hoops and managing retries etc.

sorentwo

sorentwo

Oban Core Team

Some benchmarks are included in the Oban repo. The variance is down to two factors:

  1. The concurrency limit
  2. The cool down period

With a cool down of 1ms and a concurrency of 1, you can run at most 1k in a second. With a more realistic concurrency of 10 you can run 10k in a minute.

Most of my benchmarking focuses on throughput, or how many jobs can be processed with sustained inserts and execution simultaneously.

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews