StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Background Jobs
  4. Message Queue
  5. Disque vs pg-amqp-bridge

Disque vs pg-amqp-bridge

OverviewComparisonAlternatives

Overview

Disque
Disque
Stacks11
Followers25
Votes0
GitHub Stars8.1K
Forks537
pg-amqp-bridge
pg-amqp-bridge
Stacks0
Followers7
Votes0
GitHub Stars374
Forks38

Disque vs pg-amqp-bridge: What are the differences?

  1. Data storage : Disque stores its data in-memory, providing high performance for real-time data processing, while pg-amqp-bridge stores its data in PostgreSQL, allowing for durable and persistent storage of messages.
  2. Integration with RabbitMQ : Disque is a standalone system and does not directly integrate with RabbitMQ, while pg-amqp-bridge acts as a bridge between PostgreSQL and RabbitMQ, facilitating seamless communication between the two systems.
  3. System dependencies : Disque does not have any external dependencies, making it easy to deploy and manage, whereas pg-amqp-bridge requires PostgreSQL and RabbitMQ to be installed and configured separately.
  4. Scalability : Disque can easily scale horizontally by adding more nodes to the cluster, providing scalability for increased workloads, whereas pg-amqp-bridge does not inherently support horizontal scaling and may require additional configurations for distributed setups.
  5. Message processing : Disque focuses on fast data processing and real-time message handling, making it suitable for high-throughput applications, while pg-amqp-bridge emphasizes data persistence and reliability, catering to scenarios where message durability is critical.
  6. Community support : Disque has a smaller user base and community compared to pg-amqp-bridge, which is more established and has a broader range of resources and documentation available for users.

In Summary, Disque and pg-amqp-bridge differ in their data storage mechanisms, integration capabilities, system dependencies, scalability options, message processing priorities, and community support.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Disque
Disque
pg-amqp-bridge
pg-amqp-bridge

Disque is an ongoing experiment to build a distributed, in-memory, message broker. Its goal is to capture the essence of the "Redis as a jobs queue" use case, which is usually implemented using blocking list operations, and move it into an ad-hoc, self-contained, scalable, and fault tolerant design, with simple to understand properties and guarantees, but still resembling Redis in terms of simplicity, performance, and implementation as a C non-blocking networked server.

This tool enables a decoupled architecture, think sending emails when a user signs up. Instead of having explicit code in your signup function that does the work (and slows down your response), you just have to worry about inserting the row into the database.

Statistics
GitHub Stars
8.1K
GitHub Stars
374
GitHub Forks
537
GitHub Forks
38
Stacks
11
Stacks
0
Followers
25
Followers
7
Votes
0
Votes
0
Integrations
No integrations available
PostgreSQL
PostgreSQL
RabbitMQ
RabbitMQ

What are some alternatives to Disque, pg-amqp-bridge?

Kafka

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

RabbitMQ

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Celery

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

ActiveMQ

ActiveMQ

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

ZeroMQ

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Apache NiFi

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Gearman

Gearman

Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.

Memphis

Memphis

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase