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 VerneMQ

Azure Service Bus vs VerneMQ

OverviewDecisionsComparisonAlternatives

Overview

VerneMQ
VerneMQ
Stacks31
Followers136
Votes6
Azure Service Bus
Azure Service Bus
Stacks553
Followers536
Votes7

Azure Service Bus vs VerneMQ: What are the differences?

What is Azure Service Bus? *Reliable cloud messaging as a service (MaaS) *. 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.

What is VerneMQ? VerneMQ is a distributed IoT/MQTT message broker. VerneMQ is a distributed MQTT message broker, implemented in Erlang/OTP It's open source, and Apache 2 licensed. VerneMQ implements the MQTT 3.1, 3.1.1 and 5.0 specifications..

Azure Service Bus and VerneMQ belong to "Message Queue" category of the tech stack.

VerneMQ is an open source tool with 1.79K GitHub stars and 191 GitHub forks. Here's a link to VerneMQ's open source repository on GitHub.

Yammer, OneWire, and eMarketer, Inc. are some of the popular companies that use Azure Service Bus, whereas VerneMQ is used by Haptik, Cantiz, and Teleolabs. Azure Service Bus has a broader approval, being mentioned in 11 company stacks & 8 developers stacks; compared to VerneMQ, which is listed in 4 company stacks and 6 developer stacks.

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 VerneMQ, 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

VerneMQ
VerneMQ
Azure Service Bus
Azure Service Bus

VerneMQ is a distributed MQTT message broker, implemented in Erlang/OTP. It's open source, and Apache 2 licensed. VerneMQ implements the MQTT 3.1, 3.1.1 and 5.0 specifications.

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.

Open Source, Apache 2 licensed; QoS 0, QoS 1, QoS 2; MQTT v5.0 fully implemented; Basic Authentication and Authorization; Bridge Support; $SYS Tree for monitoring and reporting; TLS (SSL) Encryption; Websockets Support; Cluster Support with sophisticated self-healing mechanisms; Queue Migration; Prometheus Monitoring; Logging (Console, Files, Syslog); Reporting to Graphite; Extensible Plugin architecture (Erlang, Elixir, Lua); WebHooks Plugins; Multiple Sessions per ClientId; Shared Subscriptions; Proxy Protocol v1, v2;
-
Statistics
Stacks
31
Stacks
553
Followers
136
Followers
536
Votes
6
Votes
7
Pros & Cons
Pros
  • 1
    Fully open source clustering
  • 1
    MQTT v5 implementation
  • 1
    Open Source Message and Metadata Persistence
  • 1
    Open Source Plugin System
  • 1
    Proxy Protocol support
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
Integrations
MySQL
MySQL
MongoDB
MongoDB
PostgreSQL
PostgreSQL
Memcached
Memcached
Redis
Redis
No integrations available

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

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