Making Postgres queues scale

Discussion (6 Comments)Read Original on HackerNews

dewey•about 2 hours ago

> The conventional wisdom around Postgres-backed queues is that they don't scale.

That might have been the case 10 years ago. In the past years there have been many Postgres powered queueing systems and even Rails switched to Postgres powered queues by default (SolidQueue) more than 3 years ago.

mjfisher•15 minutes ago

I see a lot of back and forth about postgres' suitability as a queuing system. I wonder if there's a couple of separable problems here. Postgres backed queues - even very scalable ones - might work well for background jobs in a monolithic app backed by a single DB. Things like backgrounding sending an email etc.

But usually when I reach for a queuing system, it's because I want to decouple a part of the architecture. And in that case, it's probably better to use a dedicated queueing system instead of postgres.

I wonder if the two cases are conflated in a lot of online discussion.

sorentwo•about 1 hour ago

They certainly do, and I don't think it's a controversial take at this point.

Shameless link to an older article about throughput with Oban (https://oban.pro/articles/one-million-jobs-a-minute-with-oba...), and in follow-up research we've sustained 12k/s with a p99 under ~100ms.

richwater•27 minutes ago

Reading Postgres queuing posts always seem like deja vu. People love to write about them

mlnj•25 minutes ago

These days, most of them are from the DBOS folks. :)

tonyhb•10 minutes ago

indeed, every ~week with essentially the same thing: skip locked.

Making Postgres queues scale

⚡ Community Insights

Discussion (6 Comments)Read Original on HackerNews