For some reason many Django developers choose the Django database as a Celery message broker and a result backend. Maybe they don’t want to bring in more third-party software like RabbitMQ or Redis, but performance and stability suffer a lot.
The Django database is not a recommended Celery message broker. It’s experimental and not suitable for production. Plus, it has serious limitations because it does not support remote control commands, events and the usage of more than a few workers.