From d3f142f2cd36ba0458cc679397555bd5ee7db744 Mon Sep 17 00:00:00 2001 From: Jacob Walls Date: Tue, 2 Dec 2025 10:25:26 -0500 Subject: Refs #35859 -- Clarified Tasks ref and topics docs regarding available backends. --- docs/ref/tasks.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'docs/ref') diff --git a/docs/ref/tasks.txt b/docs/ref/tasks.txt index c427c4c4d3..99d8eb6a0a 100644 --- a/docs/ref/tasks.txt +++ b/docs/ref/tasks.txt @@ -7,6 +7,10 @@ Tasks .. module:: django.tasks :synopsis: Django's built-in background Task system. +The Task framework provides the contract and plumbing for background work, not +the engine that runs it. The Tasks API defines how work is described, queued, +and tracked, but leaves actual execution to external infrastructure. + Task definition =============== @@ -274,6 +278,10 @@ Task errors Backends ======== +Backends handle how Tasks are stored and executed. All backends share a common +interface defined by ``BaseTaskBackend``, which specifies the core methods for +enqueueing Tasks and retrieving results. + Base backend ------------ @@ -365,6 +373,10 @@ Feature :class:`.DummyBackend` :class:`.ImmediateBackend` Available backends ------------------ +Django includes only development and testing backends. These support local +execution and inspection, for production ready backends refer to +:ref:`configuring-a-task-backend`. + Immediate backend ~~~~~~~~~~~~~~~~~ -- cgit v1.3