> To make all of this run smoothly, we enqueue and dequeue thousands of jobs every day. The scale isn't large enough for this to at all be a worry. The biggest

> To make all of this run smoothly, we enqueue and dequeue thousands of jobs every day. The scale isn't large enough for this to at all be a worry. The biggest worry here I imagine is ensuring that a job isn't processed by multiple workers, which they solve with features built into Postgres. Usually I caution against using a database as a queue, but in this case it removes a piece of the architecture that they have to manage and they're clearly more comfortable with SQL than RabbitMQ so it sounds like a good call.