Celery vs RSMQ | What are the differences? | StackShare

Celery vs RSMQ

Overview

Celery

Stacks1.7K

Followers1.6K

Votes280

GitHub Stars27.5K

Forks4.9K

RSMQ

Stacks4

Followers87

Votes6

GitHub Stars1.8K

Forks120

Celery vs RSMQ: What are the differences?

Celery: Distributed task queue. 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; RSMQ: A lightweight message queue for Node.js that requires no dedicated queue server. Just a Redis server. tl;dr: If you run a Redis server and currently use Amazon SQS or a similar message queue you might as well use this fast little replacement. Using a shared Redis server multiple Node.js processes can send / receive messages.

Celery and RSMQ can be primarily classified as "Message Queue" tools.

Celery and RSMQ are both open source tools. It seems that Celery with 12.9K GitHub stars and 3.33K forks on GitHub has more adoption than RSMQ with 1.07K GitHub stars and 78 GitHub forks.

🔥 Trending in Background Jobs on StackShare

Solid Queue Background Jobs

Database-backed active job backend

Try it View Docs Alternatives

Try

Advice on Celery, RSMQ

Shantha

Sep 30, 2020

Needs adviceon

RabbitMQ

Celery

MongoDB

I am just a beginner at these two technologies.

Problem statement: I am getting lakh of users from the sequel server for whom I need to create caches in MongoDB by making different REST API requests.

Here these users can be treated as messages. Each REST API request is a task.

I am confused about whether I should go for RabbitMQ alone or Celery.

If I have to go with RabbitMQ, I prefer to use python with Pika module. But the challenge with Pika is, it is not thread-safe. So I am not finding a way to execute a lakh of API requests in parallel using multiple threads using Pika.

If I have to go with Celery, I don't know how I can achieve better scalability in executing these API requests in parallel.

334k views334k

Comments

Detailed Comparison

Celery	RSMQ
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.	tl;dr: If you run a Redis server and currently use Amazon SQS or a similar message queue you might as well use this fast little replacement. Using a shared Redis server multiple Node.js processes can send / receive messages.
-	Lightweight: Just Redis and ~500 lines of javascript.;Guaranteed delivery of a message to exactly one recipient within a messages visibility timeout.;Received messages that are not deleted will reappear after the visibility timeout.;Test coverage;Optional RESTful interface via rest-rsmq
Statistics
GitHub Stars 27.5K	GitHub Stars 1.8K
GitHub Forks 4.9K	GitHub Forks 120
Stacks 1.7K	Stacks 4
Followers 1.6K	Followers 87
Votes 280	Votes 6
Pros & Cons
Pros 99 Task queue 63 Python integration 40 Django integration 30 Scheduled Task 19 Publish/subsribe Cons 4 Sometimes loses tasks 1 Depends on broker	Pros 2 Simple, does one thing well 1 Written in TypeScript 1 Backed by Redis 1 Written in Coffeescript 1 Comes with a visibility timeout feature similar to AWS
Integrations
No integrations available	Redis

What are some alternatives to Celery, RSMQ?

Kafka

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

RabbitMQ

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

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 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

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.

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

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 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.

Memphis

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

IronMQ

An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.