The latest articles on DEV Community by Cameron Bennett (@camerondev). https://dev.to/camerondev https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210932%2F729fd630-5030-48b0-888d-fbad678cc429.jpg https://dev.to/camerondev en Cameron Bennett Tue, 27 Oct 2026 15:50:55 +0000 https://dev.to/camerondev/go-postgres-and-the-queue-i-didnt-need-3f2g https://dev.to/camerondev/go-postgres-and-the-queue-i-didnt-need-3f2g <p>I added Redis and a job queue to a service before it had any real traffic. A year later, I removed both.</p> <p>The traffic was maybe 20 writes per minute. Postgres could handle that with a simple <code>SKIP LOCKED</code> worker loop and a status column. No extra service, no extra failure mode.</p> <p>What I kept from the experiment:</p> <ul> <li>The worker interface (so I can swap the backend later)</li> <li>The metrics and retry policy</li> </ul> <p>What I removed:</p> <ul> <li>Redis</li> <li>The queue library</li> <li>A deployment and a set of alerts</li> </ul> <p>The lesson isn't "never use a queue." It's "earn your infrastructure." Start with the database you already have.</p> <p>I'm reading about SQLite internals for a side project. The more I learn about storage engines, the more I appreciate Postgres.</p> go postgres backend