Question 1

How does Rihanna compare to Oban for Elixir job queues?

Accepted Answer

Rihanna uses PostgreSQL advisory locks for speed and supports arbitrary Elixir terms, while Oban offers more built-in features like cron jobs and multiple queues. Both provide ACID guarantees, but Rihanna is simpler with no extra dependencies, whereas Oban has a richer ecosystem.

Question 2

How to set up recurring jobs in Rihanna?

Accepted Answer

Implement a job that reschedules itself after completion using Rihanna.schedule, ensuring Postgres ACID guarantees for continuity. You'll need to manually enqueue the first instance, as mentioned in the FAQs for cron-like tasks.

Question 3

What happens to running jobs when I deploy my Elixir app?

Accepted Answer

Running jobs are terminated during application restarts, such as deployments, because the BEAM exits. The README advises keeping jobs short or designing them to handle interruptions gracefully.

Question 4

Can Rihanna handle millions of jobs per day?

Accepted Answer

Yes, with a cap of around 10,000 jobs per second per the README, it can process millions daily, but performance depends on your PostgreSQL setup. For higher volumes, consider dedicated messaging systems.

Question 5

Is Rihanna good for real-time processing or only background tasks?

Accepted Answer

It's designed for background job processing with scheduling and durability, not real-time streaming. Jobs run asynchronously with configurable concurrency, making it ideal for deferred work rather than instant messaging.

Question 6

How do I monitor failed jobs in Rihanna?

Accepted Answer

Use the built-in Rihanna UI web interface to inspect, delete, and retry failed jobs visually. Alternatively, you can query the rihanna_jobs table directly for programmatic monitoring.

Rihanna

What is Rihanna?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions