2 ms·
My understanding is that if you just need to return a response to the client as quickly as possible, but are ok with then processing your task directly after th
by ranger_danger 1y ago
My understanding is that if you just need to return a response to the client as quickly as possible, but are ok with then processing your task directly after that, then it's still usable today.
But if you want to schedule a task further in the future, then a new backend will be needed for that.
- dabeeeenster 1y agoI think the bigger use case is being able to (backoff) retry failing API calls to 3rd party services. AFAIUI the new tasks package doesnt offer this in v1 which is a deal breaker for my project, at least.
- majorchord 1y agoFor me I think it works well as is because my use case is sending several different emails after POST'ing to a view, which, there is no need to make the user wait for in my case, as they don't care about the status of the mail delivery. But I realize there are many other usecases too that will need proper workers.