<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Postgres on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/postgres/</link>
    <description>Recent content in Postgres on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 11 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/postgres/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GoodJob vs Solid Queue vs Que in 2026: Postgres-Backed Job Queues for Rails</title>
      <link>https://www.pistack.xyz/posts/2026-08-11-goodjob-solid-queue-que-postgres-job-queues-comparison/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-11-goodjob-solid-queue-que-postgres-job-queues-comparison/</guid>
      <description>&lt;p&gt;Redis has been the default home for Rails background jobs for a decade — but it is also one more service to run, monitor, back up, and pay for. Since Rails 8 shipped with Solid Queue as the default queue backend, the debate has flipped: &lt;strong&gt;do you even need Redis anymore?&lt;/strong&gt; Three mature, Postgres-only job backends now cover everything from a solo developer&amp;rsquo;s hobby app to multi-tenant production workloads: &lt;strong&gt;GoodJob&lt;/strong&gt; (2,990 stars), &lt;strong&gt;Solid Queue&lt;/strong&gt; (2,481 stars, maintained by the Rails core team), and &lt;strong&gt;Que&lt;/strong&gt; (2,323 stars, the speed demon). All three eliminate Redis entirely by storing jobs in the same Postgres database you already run. This guide compares them with real configuration, real performance characteristics, and a clear recommendation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
