3 ms·
We had evaluated Celery for our use case. There were a few things it couldn't do such as create queues dynamically with per queue rate limit. We chose Lua beca
by ohmygeek 12y ago
We had evaluated Celery for our use case. There were a few things it couldn't do such as create queues dynamically with per queue rate limit.
We chose Lua because the queue operations involve modifying more than one Redis data structure and this had to be atomic.
We'll be adding more details on why we built this and how it compares with Celery.. :)
- SEJeff 12y agoCan you please not do one thing Ask (celery author) constantly does? He breaks the celery API to a ridiculous degree between point releases. I've used celery for 5+ years and constantly have to hard fix the version I use in a requirements.txt or whatnot because the most seemingly minor point release results in broken tasks and a different api. Use semver or something sane to not make your users angry. Pretty please!