Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a...
by bsaul on Thursday April 13, 2023 @05:13AM
(#35552897)
I feel like this would reimplement a lot of the machinery that's built-in the job queue (atomic state locking to take ownership of the job, with deadlocking prevention mechanism to make sure a killed process doesn't keep that job locked, and timeouts).
At this point, why not throw the whole job queue away and simply use that system ?
At this point, why not throw the whole job queue away and simply use that system ?