Need advice about which tool to choose?Ask the StackShare community!
Beanstalkd vs Celery: What are the differences?
What is Beanstalkd? A simple, fast work queue. 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.
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.
Beanstalkd belongs to "Background Processing" category of the tech stack, while Celery can be primarily classified under "Message Queue".
"Fast" is the primary reason why developers consider Beanstalkd over the competitors, whereas "Task queue" was stated as the key factor in picking Celery.
Beanstalkd and Celery are both open source tools. It seems that Celery with 12.9K GitHub stars and 3.33K forks on GitHub has more adoption than Beanstalkd with 5.12K GitHub stars and 748 GitHub forks.
Udemy, Sentry, and Postmates are some of the popular companies that use Celery, whereas Beanstalkd is used by Douban, Rollbar, and Vigil. Celery has a broader approval, being mentioned in 272 company stacks & 77 developers stacks; compared to Beanstalkd, which is listed in 27 company stacks and 8 developer stacks.
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 Beanstalkd
- Fast23
- Free12
- Does one thing well12
- Scalability9
- Simplicity8
- External admin UI developer friendly3
- Job delay3
- Job prioritization2
- External admin UI2
Pros of Celery
- Task queue99
- Python integration63
- Django integration40
- Scheduled Task30
- Publish/subsribe19
- Various backend broker8
- Easy to use6
- Great community5
- Workflow5
- Free4
- Dynamic1
Sign up to add or upvote prosMake informed product decisions
Cons of Beanstalkd
Cons of Celery
- Sometimes loses tasks4
- Depends on broker1