There's a lot more to a web application than just the request/response cycle. Running tasks in the background, whether on a trigger or schedule unlocks a lot of extra functionality, performance and reliability.
Whilst Django is a web framework, it doesn't have a good first-party story for background workers right now. When most people think of background workers, they lean immediately to Celery, but other tools are out there which might be better and easier to work with.
The lack of first-party support results in diverging implementations, added complexity for developers, and a learning cliff for new developers. If Django had a first-party solution, it could help unify these implementations, and make Django more "batteries included". The lack of first-party support is also a challenge to Wagtail, where many potentially intensive tasks have to be run in the request/response cycle, slowing down user actions.
Similar content
Bringing Background Workers to Django
- 2024-09-10
- 20 minutes
- Slides
- Django London
This talk was almost identical to the one I gave at Djangocon Europe 2024. Django London isn't recorded, but the slides are linked. If you want to watch the talk, I recommend watching the Djangocon version. There's a lot more to a web application than just the request/response cycle. Running tasks in the background, whether on a trigger or schedule unlocks a lot of extra functionality, performance and…
Django Tasks - Django Chat #200
- 2026-04-15
- 2 hours
- Video
- Django Chat
I was invited to an episode of Django Chat, to chat about Django Tasks, the Security Team and much more. I'm well aware that a podcast isn't really a "talk", but it's appropriate enough.
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.