Overview

Azure Service Bus

Stacks283

Followers536

Votes7

Amazon MQ

Stacks54

Followers325

Votes12

Amazon MQ vs Azure Service Bus: What are the differences?

Key Differences between Amazon MQ and Azure Service Bus

In this article, we will explore the key differences between Amazon MQ and Azure Service Bus. Both Amazon MQ and Azure Service Bus are managed messaging services provided by Amazon Web Services (AWS) and Microsoft, respectively. These services help businesses decouple their applications, improve reliability, and increase scalability by providing a messaging infrastructure. However, there are several differences between them.

Protocol Support: Amazon MQ supports different messaging protocols, including Advanced Message Queuing Protocol (AMQP), OpenWire, and Message Queue Telemetry Transport (MQTT). On the other hand, Azure Service Bus primarily supports the AMQP and HTTP protocols. This difference in protocol support gives customers flexibility in choosing the protocol that best suits their needs.
Deployment Model: Amazon MQ is a fully managed service that runs on Amazon's infrastructure. It can be easily provisioned and managed using the AWS Management Console. In contrast, Azure Service Bus can be deployed on-premises, in the cloud, or in a hybrid model, giving customers more deployment flexibility.
Message Ordering: Amazon MQ provides strict ordering of messages within the same message group, ensuring that messages are processed in the exact order they are received. Azure Service Bus, on the other hand, does not guarantee strict ordering of messages within a queue or topic, making it suitable for scenarios where strict ordering is not a requirement.
Feature Set: Amazon MQ offers a broader range of features compared to Azure Service Bus. For example, Amazon MQ supports broker-to-broker connectivity with Amazon ActiveMQ and RabbitMQ, while Azure Service Bus does not have this capability. Additionally, Amazon MQ provides more extensive monitoring and management features, such as performance metrics and alarms.
Pricing Model: The pricing models for Amazon MQ and Azure Service Bus differ. Amazon MQ pricing is based on the instance type and usage, while Azure Service Bus pricing is based on the number of messaging operations and data transfer. Customers should consider their specific messaging needs and choose the pricing model that aligns with their requirements.
Integration with Other Services: Both Amazon MQ and Azure Service Bus can integrate with other services in their respective cloud providers' ecosystems. However, Amazon MQ has tighter integration with other AWS services, such as Amazon SNS, Amazon SQS, and AWS Lambda, which can provide additional capabilities and flexibility for customers.

In Summary, the key differences between Amazon MQ and Azure Service Bus include protocol support, deployment model, message ordering, feature set, pricing model, and integration with other services. These differences allow customers to select the messaging service that best fits their specific requirements and preferences.

Advice on Azure Service Bus, Amazon MQ

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

MITHIRIDI

Software Engineer at LightMetrics

May 8, 2020

Needs adviceon

Amazon SQS

Amazon MQ

I want to schedule a message. Amazon SQS provides a delay of 15 minutes, but I want it in some hours.

Example: Let's say a Message1 is consumed by a consumer A but somehow it failed inside the consumer. I would want to put it in a queue and retry after 4hrs. Can I do this in Amazon MQ? I have seen in some Amazon MQ videos saying scheduling messages can be done. But, I'm not sure how.

303k views303k

Comments

Detailed Comparison

Azure Service Bus	Amazon MQ
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.	Amazon MQ is a managed message broker service for Apache ActiveMQ that makes it easy to set up and operate message brokers in the cloud.
Statistics
Stacks 283	Stacks 54
Followers 536	Followers 325
Votes 7	Votes 12
Pros & Cons
Pros 4 Easy Integration with .Net 2 Cloud Native 1 Use while high messaging need Cons 1 Limited features in Basic tier 1 Skills can only be used in Azure - vendor lock-in 1 Observability of messages in the queue is lacking 1 Lacking in JMS support	Pros 7 Supports low IQ developers 3 Supports existing protocols (JMS, NMS, AMQP, STOMP, …) 2 Easy to migrate existing messaging service Cons 4 Slow AF
Integrations
No integrations available	AWS IAM Amazon CloudWatch ActiveMQ

What are some alternatives to Azure Service Bus, Amazon MQ?

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.