35 engineers on Hacker News describe using Celery first-hand: 2 endorse it, 11 regret it, 4 are mixed.
“My top problem with my celery setup has always been visibility. ... The actual queue and execute part has always been easy / worked well.”
mixed · production · brianwawok · 2026-01-29 · source ↗ · wrong label?“It's been night and day in terms of visibility and tracking.”
regret · production · tecoholic · 2026-01-28 · source ↗ · wrong label?“Everyone I know who had Celery in production was looking for a substitution (custom or third-party) on a regular basis.”
regret · production · leobuskin · 2025-12-10 · source ↗ · wrong label?“We have periodic problems with celery: workers losing connection with RabbitMQ, Celery itself getting stuck”
regret · production · pmontra · 2025-11-29 · source ↗ · wrong label?“it was so buggy and so troublesome that at some point we switched to a hastily hacked own solution and it worked better”
regret · production · integralid · 2025-11-04 · source ↗ · wrong label?“After multiple years fighting with Celery, we moved to Prefect last year and have been mostly happy with it.”
regret · production · 2 yr · tecoholic · 2024-06-27 · source ↗ · wrong label?“We actually also stared with celery, but moved to SQS to improve the stability.”
regret · production · arzelaascoli · 2023-10-10 · source ↗ · wrong label?“We got a lot of mileage out of it (in a past life) before finally moving our job scheduling to a custom solution built on RQ. Celery caused more than a few headaches”
regret · production · sz3 · 2022-03-06 · source ↗ · wrong label?“We switched our python task processing from celery to pubsub... Celery is full of bugs and quirks, nobody ever really knew what it was doing when it would fail.”
regret · production · e-brake · 2022-03-06 · source ↗ · wrong label?“took longer with celery really (back on python 2.7) but that system has been in prod for 6 years now without really needing any maintenance”
mixed · production · 6 yr · robbiep · 2020-05-21 · source ↗ · wrong label?“We ditched celery after many years of use in favor of just connecting to RabbitMQ ourselves.”
regret · production · scaryclam · 2017-11-13 · source ↗ · wrong label?“Celery is indeed great, but the doc falls far behind django's. The "celery+django" doc is actually outdated in a couple of places”
mixed · personal · hobarrera · 2016-11-23 · source ↗ · wrong label?“We moved to Celery because it could use RabbitMQ as a broker.”
endorse · production · asadjb · 2016-11-13 · source ↗ · wrong label?“we use Celery in production for asynchronous number crunching... we wish there were better built-in task management”
mixed · production · k_sze · 2016-11-13 · source ↗ · wrong label?“we replaced most of our cron jobs with celery and django celery fulldbresult”
endorse · production · St-Clock · 2015-10-17 · source ↗ · wrong label?“Once deployed in production I spent countless evenings debugging why the tasks weren't running”
regret · production · 1_player · 2015-07-29 · source ↗ · wrong label?“until we switched to redis/celery. Then it became too much hassle to install these in every machine”
regret · production · StavrosK · 2010-10-08 · source ↗ · wrong label?“I've been using Celery for years. What is the major issues you have with it”
neutral · production · sgt · 2025-12-10 · source ↗ · wrong label?“I've only used celery in production before, and I'm willing to change my mind.”
neutral · production · jonatron · 2025-12-09 · source ↗ · wrong label?“Celery when background jobs are needed (optional too)”
neutral · production · level09 · 2025-12-08 · source ↗ · wrong label?“Three years ago, I worked on a project that used the software for a Celery queue.”
neutral · production · mianos · 2023-09-25 · source ↗ · wrong label?“used postgres as a database, along with rabbitmq and celery for job processing.”
neutral · production · shoo · 2021-12-18 · source ↗ · wrong label?“Celery with RabbitMQ/Redis for task processing.”
neutral · production · clepto · 2021-12-07 · source ↗ · wrong label?“I myself made that mistake, and have since gotten much better results with the aforementioned change.”
neutral · production · ben_jones · 2016-12-06 · source ↗ · wrong label?“The last site I worked on consisted of nginx, elasticsearch, logstash, kibana, postgresql, celery, redis”
neutral · production · markbnj · 2015-07-01 · source ↗ · wrong label?“We've been using the python celery task queue library to coordinate python ETL-esque jobs”
neutral · production · mycelium · 2015-06-23 · source ↗ · wrong label?“In our environment we run tasks on RabbitMQ/Celery.”
neutral · production · LukaAl · 2015-05-20 · source ↗ · wrong label?“We deploy our Celery workers under separate Docker containers”
neutral · production · boffbowsh · 2014-12-08 · source ↗ · wrong label?“MRQ is heavily inspired by RQ to which we switched from Celery”
neutral · production · sylvinus · 2014-06-19 · source ↗ · wrong label?“Guide images are pushed to S3 by Celery, and we're using MySQL as the database”
neutral · production · tomkinstinch · 2014-05-16 · source ↗ · wrong label?“we run some asynchronous tasks with Go now, specifying to replace a few things that were done by Celery previously.”
neutral · production · mattrobenolt · 2014-05-07 · source ↗ · wrong label?“For Fashiolista we currently use celery with rabbitmq and have different queues and worker clusters”
neutral · production · tschellenbach · 2013-10-15 · source ↗ · wrong label?“our application servers (running Django, memcached and celery workers)”
neutral · production · simonw · 2012-11-13 · source ↗ · wrong label?“using tastypie for the api side and celery for offline tasks”
neutral · production · Fledeskum · 2012-05-22 · source ↗ · wrong label?“I already had RabbitMQ set up and routing background tasks for celery”
neutral · production · wooster · 2010-03-31 · source ↗ · wrong label?