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. ZeroMQ vs pg-amqp-bridge

ZeroMQ vs pg-amqp-bridge

OverviewDecisionsComparisonAlternatives

Overview

ZeroMQ
ZeroMQ
Stacks258
Followers586
Votes71
GitHub Stars10.6K
Forks2.5K
pg-amqp-bridge
pg-amqp-bridge
Stacks0
Followers7
Votes0
GitHub Stars374
Forks38

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

# ZeroMQ vs pg-amqp-bridge

ZeroMQ and pg-amqp-bridge are two popular messaging libraries used for communication between different components of a system. Here are the key differences between ZeroMQ and pg-amqp-bridge:

1. **Transport Protocol**: ZeroMQ uses its own transport protocols for messaging, while pg-amqp-bridge specifically supports the AMQP (Advanced Message Queuing Protocol) standard.
2. **Database Integration**: pg-amqp-bridge is designed for integrating Postgres databases with messaging queues, while ZeroMQ is a more general-purpose messaging library that can be used in a variety of applications.
3. **Official Support**: ZeroMQ is maintained by a community-driven organization, while pg-amqp-bridge is officially supported by the team behind Postgres.
4. **Complexity**: ZeroMQ is known for its simplicity and ease of use, making it ideal for straightforward messaging scenarios. On the other hand, pg-amqp-bridge may have more complexity due to its specific focus on Postgres integration.
5. **Scalability**: ZeroMQ is highly scalable and allows for building distributed systems with minimal effort, whereas pg-amqp-bridge may have limitations in scalability depending on the workload and the database used.
6. **Performance**: In terms of performance, ZeroMQ is generally faster due to its lightweight nature and direct communication approach, while pg-amqp-bridge may introduce additional overhead due to the AMQP protocol and database integration.

In Summary, ZeroMQ and pg-amqp-bridge differ in their transport protocols, database integration, official support, complexity, scalability, and performance characteristics.

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

Advice on ZeroMQ, pg-amqp-bridge

Meili
Meili

Software engineer at Digital Science

Sep 24, 2020

Needs adviceonZeroMQZeroMQRabbitMQRabbitMQAmazon SQSAmazon SQS

Hi, we are in a ZMQ set up in a push/pull pattern, and we currently start to have more traffic and cases that the service is unavailable or stuck. We want to:

  • Not loose messages in services outages
  • Safely restart service without losing messages (@{ZeroMQ}|tool:1064| seems to need to close the socket in the receiver before restart manually)

Do you have experience with this setup with ZeroMQ? Would you suggest RabbitMQ or Amazon SQS (we are in AWS setup) instead? Something else?

Thank you for your time

500k views500k
Comments
Bela Tibor
Bela Tibor

Technical Lead at Salt & Pepper

Mar 10, 2021

Review

This depends on your needs, but basically Kafka is the de-facto solution to go for. RabbitMQ, ZeroMQ or similar message queuing systems have their advantages too. Check for parallel consuming, in-flight queue (topic for Kafka) creation needs, consumer <-> message relations (how many consumers are interested in a message, all consumers are interested in all messages) etc...

65 views65
Comments

Detailed Comparison

ZeroMQ
ZeroMQ
pg-amqp-bridge
pg-amqp-bridge

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.

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.

Connect your code in any language, on any platform.;Carries messages across inproc, IPC, TCP, TPIC, multicast.;Smart patterns like pub-sub, push-pull, and router-dealer.;High-speed asynchronous I/O engines, in a tiny library.;Backed by a large and active open source community.;Supports every modern language and platform.;Build any architecture: centralized, distributed, small, or large.;Free software with full commercial support.
-
Statistics
GitHub Stars
10.6K
GitHub Stars
374
GitHub Forks
2.5K
GitHub Forks
38
Stacks
258
Stacks
0
Followers
586
Followers
7
Votes
71
Votes
0
Pros & Cons
Pros
  • 23
    Fast
  • 20
    Lightweight
  • 11
    Transport agnostic
  • 7
    No broker required
  • 4
    Low level APIs are in C
Cons
  • 5
    No message durability
  • 3
    Not a very reliable system - message delivery wise
  • 1
    M x N problem with M producers and N consumers
No community feedback yet
Integrations
No integrations available
PostgreSQL
PostgreSQL
RabbitMQ
RabbitMQ

What are some alternatives to ZeroMQ, 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.

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.

IronMQ

IronMQ

An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.

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