Yeah most definitely, I had a look at Django Q with Redis but I just didn't feel that it was as versatile as Celery hence I just use Celery for myself.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Just for clarificarion: Django 3.0 (and soon 3.1) Django have and will have more support for async: docs.djangoproject.com/en/3.1/topi...
And, for the Celery part, it is great. The caveat is that its hard to configure it right. There are alternatives, though.
Django RQ: github.com/rq/django-rq
Dramatiq: github.com/Bogdanp/dramatiq
Huey: huey.readthedocs.io/en/1.11.0/djan...
They are simpler (not as powerful, of course) but depending on the async task(s) trying to be achieved, they very well can suit.
Yeah most definitely, I had a look at Django Q with Redis but I just didn't feel that it was as versatile as Celery hence I just use Celery for myself.