Azure Service Bus vs Mosquitto

Overview

Mosquitto

Stacks136

Followers306

Votes14

Azure Service Bus

Stacks553

Followers536

Votes7

Azure Service Bus vs Mosquitto: What are the differences?

Deployment: Azure Service Bus is a fully managed service provided by Microsoft Azure, which means users do not have to worry about maintaining the underlying infrastructure. On the other hand, Mosquitto is an open-source message broker that users need to install and operate on their own servers or cloud instances.
Protocol Support: Azure Service Bus supports the Advanced Message Queuing Protocol (AMQP) and HTTP protocols, making it suitable for a wide range of enterprise applications. Mosquitto, however, primarily supports the Message Queuing Telemetry Transport (MQTT) protocol, which is popular for IoT applications.
Scalability: Azure Service Bus offers high scalability and can handle large workloads with ease. It provides features such as topic-based pub/sub messaging and partitioned queues for efficient message processing. Mosquitto, being a lightweight message broker, may not scale as seamlessly as Azure Service Bus in heavily loaded environments.
Authentication and Authorization: Azure Service Bus integrates with Azure Active Directory for authentication and authorization, providing enterprise-grade security features. Mosquitto, while offering basic username/password authentication, may require additional setup for robust security measures.
Monitoring and Management: Azure Service Bus includes built-in monitoring tools and management capabilities through Azure portal, allowing users to track message delivery, manage queues, and set up alerts. In contrast, Mosquitto may require third-party monitoring tools or manual configuration for monitoring message traffic and broker performance.
Pricing: Azure Service Bus follows a pay-as-you-go pricing model based on the usage of resources such as messages, operations, and data transfer. Mosquitto, being open-source, is free to use but may incur costs for hosting and maintenance of the underlying infrastructure.

In Summary, Azure Service Bus and Mosquitto differ in their deployment models, protocol support, scalability, authentication, monitoring capabilities, and pricing structures.

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)

Manual

Advice on Mosquitto, Azure Service Bus

André

Technology Manager at GS1 Portugal - Codipor

Jul 30, 2020

Needs adviceon

.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

Mosquitto	Azure Service Bus
It is lightweight and is suitable for use on all devices from low power single board computers to full servers.. The MQTT protocol provides a lightweight method of carrying out messaging using a publish/subscribe model. This makes it suitable for Internet of Things messaging such as with low power sensors or mobile devices such as phones, embedded computers or microcontrollers.	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.
Statistics
Stacks 136	Stacks 553
Followers 306	Followers 536
Votes 14	Votes 7
Pros & Cons
Pros 10 Simple and light 4 Performance	Pros 4 Easy Integration with .Net 2 Cloud Native 1 Use while high messaging need Cons 1 Observability of messages in the queue is lacking 1 Lacking in JMS support 1 Skills can only be used in Azure - vendor lock-in 1 Limited features in Basic tier

What are some alternatives to Mosquitto, Azure Service Bus?

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 gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

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

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

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

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

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

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

Azure Service Bus vs Mosquitto: What are the differences?

Deployment: Azure Service Bus is a fully managed service provided by Microsoft Azure, which means users do not have to worry about maintaining the underlying infrastructure. On the other hand, Mosquitto is an open-source message broker that users need to install and operate on their own servers or cloud instances.
Protocol Support: Azure Service Bus supports the Advanced Message Queuing Protocol (AMQP) and HTTP protocols, making it suitable for a wide range of enterprise applications. Mosquitto, however, primarily supports the Message Queuing Telemetry Transport (MQTT) protocol, which is popular for IoT applications.
Scalability: Azure Service Bus offers high scalability and can handle large workloads with ease. It provides features such as topic-based pub/sub messaging and partitioned queues for efficient message processing. Mosquitto, being a lightweight message broker, may not scale as seamlessly as Azure Service Bus in heavily loaded environments.
Authentication and Authorization: Azure Service Bus integrates with Azure Active Directory for authentication and authorization, providing enterprise-grade security features. Mosquitto, while offering basic username/password authentication, may require additional setup for robust security measures.
Monitoring and Management: Azure Service Bus includes built-in monitoring tools and management capabilities through Azure portal, allowing users to track message delivery, manage queues, and set up alerts. In contrast, Mosquitto may require third-party monitoring tools or manual configuration for monitoring message traffic and broker performance.
Pricing: Azure Service Bus follows a pay-as-you-go pricing model based on the usage of resources such as messages, operations, and data transfer. Mosquitto, being open-source, is free to use but may incur costs for hosting and maintenance of the underlying infrastructure.

In Summary, Azure Service Bus and Mosquitto differ in their deployment models, protocol support, scalability, authentication, monitoring capabilities, and pricing structures.

Azure Service Bus vs Mosquitto

Overview