CobaltHorizon | 3 years ago | on: SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue
This is interesting because I’ve seen a queue that was implemented in Postgres that had performance problems before: the job which wrote new work to the queue table would have DB contention with the queue marking the rows as processed. I wonder if they have the same problem but the scale is such that it doesn’t matter or if they’re marking the rows as processed in a way that doesn’t interfere with rows being added.