Post #2194224
2026-05-07 21:24 UTC
I’ve never been able to articulate with specificity about my concern with using your database as your job queue, and I came across an article with concrete examples of how postgres can break down under queueing workloads:
https://richyen.com/postgres/2026/05/04/postgres_job_queue.html
There is nothing about ruby in this article, but I suspect (without verifying) it’s 100% applicable to rails database job queues.
Replies (2)
-
@jamie@zomglol.wtf 2026-05-08 00:38
@soulcutter@ruby.social Definitely applicable. Solid Queue uses `FOR UPDATE SKIP LOCKED` and GoodJob uses advisory locks. Both of those strategies are mentioned in the article.
-
@drenmi@ruby.social 2026-05-08 02:01
@soulcutter@ruby.social Great technical detail on the impedance mismatch between relational databases and job queues. But dare I say that we have collectively deluded ourselves into thinking anything below "thousands of concurrent workers" is "small"? 😇