Comparison with other task schedulers

[duf59]

Hi, thanks for this package! I watched the YouTube intro and it looks great — I'm currently testing it on one of my projects.

I'm curious how it compares to existing alternatives like django-tasks, django-rq, or django-q2? I've used django-q2 in the past, mainly with the DB backend for small-load projects, and I'm now considering reasons to migrate to something else, or not!

[cunla]

django-rq:

Originally, this package was on top of django-rq, with an additional ability to save scheduled tasks in the database (the database model part).

These days, afaik, django-rq adopted some of the admin views here, while this package adopted parts of rq for the worker, queue definition, etc.

django-q2:
I am not too familiar with django-q2. It would be great if someone could do a comparison of all the features.

Genearlly speaking, it would be good to create a framework to enable comparison of these packages, something in the realm of:

• Task
  • Save task data in database (django-model)
• Job
  • Callbacks
• Queue brokers (Redis/SQS/...)
• Worker
  • Communication with workers from main process
• django-admin views
  • Queue
  • Worker
  • Jobs

[vbhadrashetti3]

@cunla From your experience, which package: django-tasks, django-rq, or django-q2 - would be the best choice for development at this stage?

[cunla]

what do you think? :)