> Django’s new Tasks framework makes it easy to define and enqueue such work. It does not provide a worker mechanism to run Tasks. The actual execution must be handled by infrastructure outside Django, such as a separate process or service.
You'll likely still need an actual backend, task runner, cache implementation with a backend etc.
Based on the current state of affairs [1] you may get more structure around tasks in the app (or django packages running tasks) which is probably a nice thing. Other than that you will still need to have a backend implementation [2] and the easiest path there is (that I can think of) a Celery wrapper =)
