Amazon SQS
Fully managed message queuing service for decoupling and scaling distributed applications
Open-Source Projects
Discover top open-source software, updated regularly with real-world adoption signals.
Discover top open-source software, updated regularly with real-world adoption signals.
Lightweight PostgreSQL‑based message queue with exactly‑once delivery
PGMQ adds a simple, dependency‑free message queue to PostgreSQL, offering SQS‑compatible APIs, exact‑once delivery, delayed messages, and archiving, all via SQL functions.
PGMQ brings a lightweight, SQL‑native message queue to PostgreSQL, targeting developers and operations teams that already rely on Postgres for data storage. By exposing SQS‑compatible functions, it lets applications publish, read, and manage messages without provisioning a separate broker.
Create queues as tables, send JSON payloads, read with configurable visibility timeouts, pop for immediate deletion, and archive for long‑term retention and replay. The extension supports delayed delivery, batch operations, and works with PostgreSQL 14‑18. A broad set of client libraries (Rust, Go, Python, Java, .NET, JavaScript, etc.) enables seamless integration across languages.
Start instantly with the official Docker image that bundles PostgreSQL and the pgmq extension, or install the extension into an existing database. No background workers or external services are required—everything runs as plain SQL functions, simplifying operations and reducing infrastructure overhead.
When teams consider PGMQ, these hosted platforms usually appear on the same shortlist.
Fully managed message queuing service for decoupling and scaling distributed applications
Fully managed enterprise message broker for decoupling applications via message queues and publish/subscribe topics
Global messaging service for event ingestion and fan‑out
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Event‑driven microservices communication
Services publish events to a PGMQ queue and consume them reliably with exactly‑once semantics, eliminating external broker costs.
Delayed job processing
Schedule tasks by sending messages with a delay; workers read them after the visibility timeout, enabling simple retry and back‑off strategies.
Audit trail and replay
Archive processed messages to the built‑in archive tables, allowing later inspection or reprocessing of historical events.
Migration from AWS SQS
Replace SQS with PGMQ using the compatible API, reducing cloud dependency while keeping existing client code.
No, PGMQ operates entirely within PostgreSQL via functions; consumers poll the queue using standard SQL.
PGMQ is compatible with PostgreSQL 14 through 18.
Messages are hidden for a configurable visibility timeout; if not deleted or archived they become visible again, ensuring a single successful consumer processes each message.
Yes, install the pgmq extension into any existing PostgreSQL instance without additional services.
A pre‑built Docker image (ghcr.io/pgmq/pg18-pgmq) includes PostgreSQL with the extension ready to use.
Project at a glance
ActiveLast synced 4 days ago