SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by pritambaral on Tuesday April 11, 2023 @04:07PM (#35530768)

I've used Postgres to handle 60M jobs per second (using FOR UPDATE SKIP LOCKED) in production, for two years, on a single dual core 8GB GCE VM. Postgres goes far.

[ Parent | on HN ]

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by qskousen on Tuesday April 11, 2023 @05:27PM (#35531817)

Either you meant "per day" or you've got a really well tuned database.

[ Parent | on HN ]

Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by pritambaral on Wednesday April 12, 2023 @11:48AM (#35541719)

Ah, my bad, I mistyped. It was 60k. I should have known when I typed out my original comment, since the design goal was only around 200M per day.

[ Parent | on HN ]