Sealer user guides show that Django transactions have been committed manually before calling the work process.
I want the system to be as reliable as possible. What is the best practice to recover the accident between the committed and calling transaction transactions (i.e. ensure that the work is always called when the transaction is carried out).
BTW, I'm currently using a database-based job queue I applied this so that there is no such problem - I can send a job within the transaction I am not really sure that I Should go in
Comments
Post a Comment