# Adriano Caloiaro - Choose Postgres queue technology (Highlights)  ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/32600938) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Adriano Caloiaro]] **Full Title**:: Choose Postgres queue technology **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [adriano.fyi](https://adriano.fyi/posts/2023-09-24-choose-postgres-queue-technology/) **Host**:: [[adriano.fyi]] **Highlighted**:: [[2023-09-28]] **Created**:: [[2023-10-06]] ## Note Postgres queue technology is often overlooked due to the focus on scalability in the tech industry. However, Postgres provides built-in pub/sub and mutual exclusion features that make it an effective and efficient queue processing option for applications, particularly those with large amounts of relational data. Developers should consider the cost and tradeoffs of adopting new queue technologies and prioritize choosing boring technology that is already in use and understood well. Building with escape hatches and abstracting away the underlying queue technology can also make switching queues easier in the future. ## Highlights - SELECT * FROM jobs ORDER BY created_at FOR UPDATED SKIP LOCKED LIMIT 1 ([View Highlight](https://read.readwise.io/read/01hbd1df2jznxdk96emqn3d0tf)) ^601793695 - When we think about new database architectures, we’re hypnotized by scaling limits. If it can’t handle petabytes, or at least terabytes, it’s not in the conversation. But most applications will never see a terabyte of data, even if they’re successful. We’re using jackhammers to drive finish nails. ([View Highlight](https://read.readwise.io/read/01hbd2k5rkq2st2wrhzvbkp6ed)) ^601799013