4 ms·
Some names - Celery (massive and heavy) - Dramatiq - APScheduler - Huey Today, Redis queues, unless stricly a single process, seem to be most pain free for
by miohtama 2y ago
Some names
- Celery (massive and heavy)
- Dramatiq
- APScheduler
- Huey
Today, Redis queues, unless stricly a single process, seem to be most pain free for small scale use.
- nicktrocado 2y agoWe had a terrible time with Dramatiq; very buggy and resource-heavy. We ended up switching to SNS/SQS combo
- miohtama 2y agoFor small scale use cases resource heavy does not matter, but only the ease of use. Amazon proprietary APIs are notoriously hard to work with.
- rtpg 2y agoAh that's unfortunate, I had a pretty OK time with Dramatiq (coming off of Celery especially). But I imagine this is dependent on your scale. I think most people reading this site are working on relatively small systems (that still need background tasks!) and the fixed costs of background tasks can be reasonable. But I could be totally offbase