StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Background Jobs
  4. Message Queue
  5. RabbitMQ vs delayed_job

RabbitMQ vs delayed_job

OverviewDecisionsComparisonAlternatives

Overview

RabbitMQ
RabbitMQ
Stacks21.8K
Followers18.9K
Votes558
GitHub Stars13.2K
Forks4.0K
delayed_job
delayed_job
Stacks53
Followers65
Votes6
GitHub Stars4.8K
Forks952

RabbitMQ vs delayed_job: What are the differences?

<Write Introduction here>

1. **Scalability**: RabbitMQ is a highly scalable message broker that can handle a large number of messages per second, making it suitable for high-volume applications. On the other hand, delayed_job is more limited in scalability as it may struggle to keep up with the processing of a large number of delayed jobs, which can lead to performance issues.
2. **Reliability**: RabbitMQ provides reliable message delivery through features like message acknowledgments and message durability, ensuring that messages are not lost in case of failures. In contrast, delayed_job may not offer the same level of reliability, potentially resulting in lost or undelivered jobs in certain failure scenarios.
3. **Flexibility**: RabbitMQ supports various messaging patterns such as publish/subscribe, point-to-point, and request/reply, offering more flexibility in designing communication between components. Delayed_job, on the other hand, is primarily focused on executing background jobs without providing extensive support for different messaging patterns.
4. **Real-time vs Delayed Processing**: RabbitMQ is designed for real-time message processing, enabling immediate delivery and consumption of messages by consumers. In contrast, delayed_job is specifically designed for executing background jobs after a certain delay, making it more suitable for tasks that can be deferred.
5. **Language Support**: RabbitMQ supports a wide range of programming languages, making it a versatile choice for developers using different technologies. Delayed_job, on the other hand, is more closely tied to the Ruby on Rails ecosystem, limiting its use in environments where other languages are predominant.
6. **Monitoring and Management**: RabbitMQ provides extensive monitoring and management capabilities through its management plugin, allowing administrators to track message flow, monitor queues, and configure settings easily. Delayed_job may lack such comprehensive monitoring and management features, requiring additional tooling for effective oversight of background job processing.

In Summary, RabbitMQ and delayed_job differ in scalability, reliability, flexibility, real-time vs delayed processing, language support, and monitoring capabilities when it comes to handling messaging and background job processing tasks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on RabbitMQ, delayed_job

viradiya
viradiya

Apr 12, 2020

Needs adviceonAngularJSAngularJSASP.NET CoreASP.NET CoreMSSQLMSSQL

We are going to develop a microservices-based application. It consists of AngularJS, ASP.NET Core, and MSSQL.

We have 3 types of microservices. Emailservice, Filemanagementservice, Filevalidationservice

I am a beginner in microservices. But I have read about RabbitMQ, but come to know that there are Redis and Kafka also in the market. So, I want to know which is best.

933k views933k
Comments
André
André

Technology Manager at GS1 Portugal - Codipor

Jul 30, 2020

Needs adviceon.NET Core.NET Core

Hello dear developers, our company is starting a new project for a new Web App, and we are currently designing the Architecture (we will be using .NET Core). We want to embark on something new, so we are thinking about migrating from a monolithic perspective to a microservices perspective. We wish to containerize those microservices and make them independent from each other. Is it the best way for microservices to communicate with each other via ESB, or is there a new way of doing this? Maybe complementing with an API Gateway? Can you recommend something else different than the two tools I provided?

We want something good for Cost/Benefit; performance should be high too (but not the primary constraint).

Thank you very much in advance :)

461k views461k
Comments
mediafinger
mediafinger

Feb 13, 2019

ReviewonKafkaKafkaRabbitMQRabbitMQ

The question for which Message Queue to use mentioned "availability, distributed, scalability, and monitoring". I don't think that this excludes many options already. I does not sound like you would take advantage of Kafka's strengths (replayability, based on an even sourcing architecture). You could pick one of the AMQP options.

I would recommend the RabbitMQ message broker, which not only implements the AMQP standard 0.9.1 (it can support 1.x or other protocols as well) but has also several very useful extensions built in. It ticks the boxes you mentioned and on top you will get a very flexible system, that allows you to build the architecture, pick the options and trade-offs that suite your case best.

For more information about RabbitMQ, please have a look at the linked markdown I assembled. The second half explains many configuration options. It also contains links to managed hosting and to libraries (though it is missing Python's - which should be Puka, I assume).

159k views159k
Comments

Detailed Comparison

RabbitMQ
RabbitMQ
delayed_job
delayed_job

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Delayed_job (or DJ) encapsulates the common pattern of asynchronously executing longer tasks in the background. It is a direct extraction from Shopify where the job table is responsible for a multitude of core tasks.

Robust messaging for applications;Easy to use;Runs on all major operating systems;Supports a huge number of developer platforms;Open source and commercially supported
-
Statistics
GitHub Stars
13.2K
GitHub Stars
4.8K
GitHub Forks
4.0K
GitHub Forks
952
Stacks
21.8K
Stacks
53
Followers
18.9K
Followers
65
Votes
558
Votes
6
Pros & Cons
Pros
  • 235
    It's fast and it works with good metrics/monitoring
  • 80
    Ease of configuration
  • 60
    I like the admin interface
  • 52
    Easy to set-up and start with
  • 22
    Durable
Cons
  • 9
    Too complicated cluster/HA config and management
  • 6
    Needs Erlang runtime. Need ops good with Erlang runtime
  • 5
    Configuration must be done first, not by your code
  • 4
    Slow
Pros
  • 3
    Easy to get started
  • 2
    Reliable
  • 1
    Doesn't require Redis

What are some alternatives to RabbitMQ, delayed_job?

Kafka

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

Sidekiq

Sidekiq

Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.

Celery

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

ActiveMQ

ActiveMQ

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

Beanstalkd

Beanstalkd

Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.

ZeroMQ

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Apache NiFi

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Gearman

Gearman

Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase