4 ms·
Yes, that's basically what we ended up doing: a queue of tasks in Postgres that a variable number of workers could access via a clever SP that encapsulated all
by orthoxerox 4y ago
Yes, that's basically what we ended up doing: a queue of tasks in Postgres that a variable number of workers could access via a clever SP that encapsulated all inter-task conflicts and spat out the next task you were allowed to process.
- j45 4y agoThere are some good business process management tools that could manage that mapping instead of the clever SP, but you have me intrigued. Are there any links that could be helpful to work through the programs and caveats of such a SP? Part of it for me is creating a table that can store the process in the database to be able to traverse it reasonably.
- orthoxerox 4y agoIt was basically a more complicated version of this: https://stackoverflow.com/questions/68809885/how-to-select-for-update-one-row-from-table-a-and-all-joined-rows-from-table-b-i https://stackoverflow.com/questions/68809885/how-to-select-f...
- j45 3y agoNice, thanks!