Need advice about which tool to choose?Ask the StackShare community!
Celery vs Apache RocketMQ: What are the differences?
What is 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.
What is Apache RocketMQ? Open source distributed messaging and streaming data platform. Apache RocketMQ is a distributed messaging and streaming platform with low latency, high performance and reliability, trillion-level capacity and flexible scalability.
Celery and Apache RocketMQ belong to "Message Queue" category of the tech stack.
Celery and Apache RocketMQ are both open source tools. It seems that Celery with 12.9K GitHub stars and 3.33K forks on GitHub has more adoption than Apache RocketMQ with 8.25K GitHub stars and 4.23K GitHub forks.
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.
For large amounts of small tasks and caches I have had good luck with Redis and RQ. I have not personally used celery but I am fairly sure it would scale well, and I have not used RabbitMQ for anything besides communication between services. If you prefer python my suggestions should feel comfortable.
Sorry I do not have a more information
Pros of Celery
- Task queue99
- Python integration63
- Django integration40
- Scheduled Task30
- Publish/subsribe19
- Various backend broker8
- Easy to use6
- Great community5
- Workflow5
- Free4
- Dynamic1
Pros of Apache RocketMQ
- Million-level message accumulation capacity in a single2
- Support tracing message and transactional message2
- BigData Friendly1
- High throughput messaging1
- Feature-rich administrative dashboard for configuration1
- Low latency1
Sign up to add or upvote prosMake informed product decisions
Cons of Celery
- Sometimes loses tasks4
- Depends on broker1