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. Azure Service Bus vs ZeroMQ

Azure Service Bus vs ZeroMQ

OverviewDecisionsComparisonAlternatives

Overview

ZeroMQ
ZeroMQ
Stacks258
Followers586
Votes71
GitHub Stars10.6K
Forks2.5K
Azure Service Bus
Azure Service Bus
Stacks553
Followers536
Votes7

Azure Service Bus vs ZeroMQ: What are the differences?

Introduction:

When comparing Azure Service Bus and ZeroMQ, it is important to understand their key differences to effectively choose the right messaging solution for your application.

1. Protocol Support: Azure Service Bus supports AMQP, MQTT, and HTTP protocols, providing flexibility for communication with various systems, while ZeroMQ uses its own lightweight protocol designed for high-performance messaging.

2. Messaging Patterns: Azure Service Bus primarily focuses on providing enterprise messaging features like message queues, topics, and subscriptions, ensuring reliable message delivery in cloud environments. On the other hand, ZeroMQ offers a more lightweight and flexible approach with different messaging patterns like pub-sub, request-reply, and pipeline.

3. Message Durability: In Azure Service Bus, messages are persisted to ensure high availability and durability through features like message streaming and dead-letter queues, while ZeroMQ does not inherently guarantee message persistence, relying on applications to handle message reliability.

4. Scalability: Azure Service Bus offers horizontal scaling by distributing message processing across multiple instances, making it suitable for handling large volumes of messages in enterprise scenarios, whereas ZeroMQ's lightweight nature makes it more suitable for localized, high-performance messaging within a single application or system.

5. Cloud Integration: Azure Service Bus seamlessly integrates with other Azure services and provides built-in security features like access control and role-based authentication, making it well-suited for cloud-native applications, whereas ZeroMQ can be integrated into a wide range of environments but may require additional security measures to be implemented.

6. Licensing and Cost: Azure Service Bus is a managed service provided by Microsoft Azure, with pricing based on usage and features, while ZeroMQ is an open-source library with no direct cost but may require additional resources for maintenance and support.

In Summary, Understanding the key differences between Azure Service Bus and ZeroMQ can help in making an informed decision based on the specific requirements of your messaging application.

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, Azure Service Bus

André
André

Technology Manager at GS1 Portugal - Codipor

Jul 30, 2020

Needs adviceon.NET Core.NET Core

Hello dear developers, our company is starting a new project for a new Web App, and we are currently designing the Architecture (we will be using .NET Core). We want to embark on something new, so we are thinking about migrating from a monolithic perspective to a microservices perspective. We wish to containerize those microservices and make them independent from each other. Is it the best way for microservices to communicate with each other via ESB, or is there a new way of doing this? Maybe complementing with an API Gateway? Can you recommend something else different than the two tools I provided?

We want something good for Cost/Benefit; performance should be high too (but not the primary constraint).

Thank you very much in advance :)

461k views461k
Comments

Detailed Comparison

ZeroMQ
ZeroMQ
Azure Service Bus
Azure Service Bus

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.

It is a cloud messaging system for connecting apps and devices across public and private clouds. You can depend on it when you need highly-reliable cloud messaging service between applications and services, even when one or more is offline.

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
-
GitHub Forks
2.5K
GitHub Forks
-
Stacks
258
Stacks
553
Followers
586
Followers
536
Votes
71
Votes
7
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
Pros
  • 4
    Easy Integration with .Net
  • 2
    Cloud Native
  • 1
    Use while high messaging need
Cons
  • 1
    Lacking in JMS support
  • 1
    Skills can only be used in Azure - vendor lock-in
  • 1
    Limited features in Basic tier
  • 1
    Observability of messages in the queue is lacking

What are some alternatives to ZeroMQ, Azure Service Bus?

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