One Developer's Case for Using Postgres as Queue, Cache, and Search Engine

A software developer in Dhaka building an AI agent side project replaced a multi-service stack — including Redis, RabbitMQ, and Elasticsearch — with a single PostgreSQL database handling all three roles. Using native Postgres features such as SKIP LOCKED for job queuing, unlogged tables for caching, and tsvector with GIN indexes for full-text search, he reduced his infrastructure to one schema, one backup strategy, and one connection pool. The approach aligns with a widely discussed essay titled 'PostgreSQL for Everything' by Raphael Bauer, which recently trended on Hacker News. Major companies including Contentful, Instacart, and The Guardian have similarly relied on Postgres for search and data management tasks traditionally offloaded to specialist systems. The developer acknowledges the patterns have limits at large scale but argues that smaller teams benefit most from consolidating multiple functions into a single, well-understood database.