Celery
Celery is a task queueing mechanism used to distribute workloads between work particles or machines. It supports asynchronous processing in distributed system architectures and can work integrated with various message intermediaries.
Celery
100celery · Queues & Streaming
Common commercial products in this category: Confluent Cloud, Amazon SQS, Amazon Kinesis
- You distribute workloads between different workpieces or machines
- You manage background operations in an asynchronous structure
- As a message tool, you use RabbitMQ, Redis, Amazon SQS, or Google Pub/Sub, storing task results in stores such as Redis, SQLAlchemy, or Django ORM.
- • High number of open issues (744)
- • NeutralHacker News
Why do we need Flask, Celery, and Redis? (2019)
“This is what I have used in the past. I think they're very convenient if you are just running one instance of uwsgi and want to share some state quickly without going through a persistent database. If you're worrying about tweaking Celery for performance, then I suspect your…”
- • NeutralHacker News
Why do we need Flask, Celery, and Redis? (2019)
“I suspect they are using a single server. I found uwsgi's mules and cache2 very useful in that situation. If someone finds that Redis and Celery are more complication than they need for a given task, then I think they're probably not using an orchestration framework.”
Verified against README · Oct 26, 2026 · source
My note
Alternative pages
More in: Queues & Streaming
- Apache Kafka★ 34,100 · today
- NSQ★ 25,772 · 2 mo ago
- Temporal★ 24,096 · today
- NATS★ 20,973 · yesterday
- Apache Pulsar★ 15,353 · today
- debezium★ 13,289 · today