---
title: "Discussion on \"Postgres as a Queue\" | Hashnode"
description: "Discussion on \"Postgres as a Queue\". Using Postgres as a job queue means building three things RabbitMQ did for free: the fetch bound, wakeup, and liveness. How DBOS and River each do it."
url: "https://hashnode.com/posts/postgres-as-a-queue/6aa661c610d3e7a1701daf86"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Postgres as a Queue](https://musashiforge.hashnode.dev/postgres-as-a-queue?utm_source=hashnode&utm_medium=feed)

Using Postgres as a job queue means building three things RabbitMQ did for free: the fetch bound, wakeup, and liveness. How DBOS and River each do it.

Sep 13 · 12 min read · musashiforge.hashnode.dev  
Updated Sep 20  
Read the article

-   [#postgres](https://hashnode.com/tag/postgres)
-   [#river](https://hashnode.com/tag/river)
-   [#celery](https://hashnode.com/tag/celery)
-   [#dbos](https://hashnode.com/tag/dbos)
-   [#temporal](https://hashnode.com/tag/temporal)
-   [#queue](https://hashnode.com/tag/queue)
-   [#durable-execution](https://hashnode.com/tag/durable-execution)
-   [#distributed-system](https://hashnode.com/tag/distributed-system)

## Written by

[sandeep kesarwani](https://hashnode.com/@musashiforge)

@musashiforge · Delhi, India

  
[View profile](https://hashnode.com/@musashiforge)

A thousand days of practice to forge. Ten thousand to refine.

I'm Sandeep. I build distributed systems at the intersection of industrial IoT, real-time analytics, and AI infrastructure. For the past 8 years, I've been the engineer who gets called when the system is on fire — OOM-killed workers, runaway queries, architectures that don't scale.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
