archive/django-background-workers-rfc
Archived
1
Fork 0
Code Activity

Nod to Wagtail RFC

Browse source 
https://github.com/wagtail/rfcs/pull/72
This commit is contained in:
Jake Howard 2024-02-07 09:44:32 +00:00
parent 9afc4b0745
commit d2acdd43f0
No known key found for this signature in database
GPG key ID: 8198AEBFA7E86782
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -7,6 +7,8 @@ For discussions, check out the [associated PR](https://github.com/RealOrangeOne/
## Abstract ## Abstract
This proposal started life as [RFC 72 for Wagtail](https://github.com/wagtail/rfcs/pull/72), but has been adapted to be generic to Django.
Django currently doesn't have a first-party solution for long-running tasks. Other frameworks such as Laravel have background workers, allowing them to push tasks into the background to be processed at a later date, without requiring the end user to wait for them to occur. Django currently doesn't have a first-party solution for long-running tasks. Other frameworks such as Laravel have background workers, allowing them to push tasks into the background to be processed at a later date, without requiring the end user to wait for them to occur.
One of the key goals behind this proposal is removing the requirement for the user to wait for tasks they don't need to, moving computation and complexity out of the request-response cycle, towards dedicated background worker processes. One of the key goals behind this proposal is removing the requirement for the user to wait for tasks they don't need to, moving computation and complexity out of the request-response cycle, towards dedicated background worker processes.