4 ms·

For anyone who's been looking for a simpler Task Queue for Django, check out Django-Q [1], it's been working very nicely for me. It doesn't have all the bells a

For anyone who's been looking for a simpler Task Queue for Django, check out Django-Q [1], it's been working very nicely for me. It doesn't have all the bells and whistles of Celery but it's very simple to get up and running using the DB as a broker and comes with periodic tasks out of the box. [1] https://django-q.readthedocs.io/en/latest/ https://django-q.readthedocs.io/en/latest/

cik 6y ago
You might also like huey (1). [1] https://github.com/coleifer/huey https://github.com/coleifer/huey
- randlet 6y ago
  I also evaluated Huey when I was looking around and it seems nice. IIRC the main reasons I chose Django-Q were 1) Built in DB as a broker (Huey is mainly focused on Redis I think) 2) Django-Q can run multiple clusters (I run in an AWS auto scaling group) and not duplicate scheduled tasks and 3) it will run on Windows (I run an OS project that is cross platform).
hallman76 6y ago
Shoutout to django-background-tasks[1] which also uses your existing database to manage the task queue. It worked really well for me. [1] https://github.com/arteria/django-background-tasks https://github.com/arteria/django-background-tasks
- randlet 6y ago
  I also checked out this one! Can't run it on multiple servers unfortunately which disqualifies it for my use (https://github.com/arteria/django-background-tasks/issues/104 https://github.com/arteria/django-background-tasks/issues/10...)
nicolaslem 6y ago
May I plug my own project? As a long time Celery user, here is what Celery would be if it were written by me: https://github.com/NicolasLM/spinach https://github.com/NicolasLM/spinach
- randlet 6y ago
  Looks nice! Especially this bit "All Spinach workers are part of the system that schedules periodic jobs, there is no need to have a pet in the cattle farm.". The fact that you can only have one celery-beat running is one of the main reasons I chose something other than Celery.

cik 6y ago

You might also like huey (1). [1] https://github.com/coleifer/huey https://github.com/coleifer/huey

randlet 6y ago
I also evaluated Huey when I was looking around and it seems nice. IIRC the main reasons I chose Django-Q were 1) Built in DB as a broker (Huey is mainly focused on Redis I think) 2) Django-Q can run multiple clusters (I run in an AWS auto scaling group) and not duplicate scheduled tasks and 3) it will run on Windows (I run an OS project that is cross platform).

hallman76 6y ago

Shoutout to django-background-tasks[1] which also uses your existing database to manage the task queue. It worked really well for me. [1] https://github.com/arteria/django-background-tasks https://github.com/arteria/django-background-tasks

randlet 6y ago
I also checked out this one! Can't run it on multiple servers unfortunately which disqualifies it for my use (https://github.com/arteria/django-background-tasks/issues/104 https://github.com/arteria/django-background-tasks/issues/10...)

nicolaslem 6y ago

May I plug my own project? As a long time Celery user, here is what Celery would be if it were written by me: https://github.com/NicolasLM/spinach https://github.com/NicolasLM/spinach

randlet 6y ago
Looks nice! Especially this bit "All Spinach workers are part of the system that schedules periodic jobs, there is no need to have a pet in the cattle farm.". The fact that you can only have one celery-beat running is one of the main reasons I chose something other than Celery.