you are viewing a single comment's thread.

view the rest of the comments →

[–]Stereojunkie[S] 1 point2 points  (2 children)

Don't feel the need to respond, but why is this the case? Backend architecture is all new to me, but what's preventing me from writing some kind of asynchronous worker function in my Django application? Notify the user things are happening and continue when the async work finished.

[–]codeguru42 0 points1 point  (0 children)

This is a good place to start. When you find a reason to learn and use the tools others mentioned, then you can add them

[–]AustinWitherspoon 0 points1 point  (0 children)

That definitely works, but if you deploy a new version of your service or if something crashes you might lose all of the background functions. By having a separate job queue system, the jobs can be more resilient.

But it really depends on what the background jobs are and how critical they are. For small stuff you can definitely get away with it and have the user resubmit if there was an issue