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. Amazon MQ vs NServiceBus

Amazon MQ vs NServiceBus

OverviewDecisionsComparisonAlternatives

Overview

NServiceBus
NServiceBus
Stacks76
Followers132
Votes2
Amazon MQ
Amazon MQ
Stacks55
Followers325
Votes12

Amazon MQ vs NServiceBus: What are the differences?

Introduction:

Key differences between Amazon MQ and NServiceBus:

  1. Messaging Protocol Support: Amazon MQ supports multiple messaging protocols like MQTT, STOMP, AMQP, and OpenWire, providing flexibility in communication standards. In contrast, NServiceBus primarily leverages the REST and SOAP protocols for messaging, limiting the variety of supported protocols for integration.

  2. Hosting Options: Amazon MQ offers a fully managed service that is maintained by Amazon Web Services (AWS), allowing users to offload the operational burden of managing message brokers. On the other hand, NServiceBus typically requires users to set up and maintain their own hosting infrastructure, providing more control but also requiring additional effort for maintenance.

  3. Scalability: Amazon MQ provides seamless scaling capabilities, making it efficient to handle varying workloads by automatically adjusting resources. In comparison, NServiceBus may require manual adjustments and configurations to accommodate increasing message volumes, potentially leading to performance bottlenecks during peak loads.

  4. Pricing Model: Amazon MQ follows a pay-as-you-go pricing model, where users are billed based on their actual usage of the messaging service. In contrast, NServiceBus typically offers a perpetual license or subscription-based pricing, which may be more cost-effective for organizations with stable messaging needs but less flexible for scaling.

  5. Monitoring and Reporting: Amazon MQ includes built-in monitoring and management tools, such as Amazon CloudWatch and AWS CloudTrail, allowing users to track performance metrics and gain insights into their messaging infrastructure. Whereas NServiceBus relies on third-party tools or custom implementations for monitoring, potentially requiring additional investment in monitoring solutions.

  6. Ease of Integration: Amazon MQ seamlessly integrates with other AWS services like EC2, Lambda, and S3, enabling broader use cases and streamlined connectivity within the AWS ecosystem. Conversely, NServiceBus may require additional development effort for integrating with complementary services outside its ecosystem, potentially adding complexity to the integration process.

In Summary, Amazon MQ and NServiceBus differ in messaging protocol support, hosting options, scalability, pricing model, monitoring capabilities, and ease of integration.

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 NServiceBus, Amazon MQ

MITHIRIDI
MITHIRIDI

Software Engineer at LightMetrics

May 8, 2020

Needs adviceonAmazon SQSAmazon SQSAmazon MQAmazon 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

NServiceBus
NServiceBus
Amazon MQ
Amazon MQ

Performance, scalability, pub/sub, reliable integration, workflow orchestration, and everything else you could possibly want in a service bus.

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
76
Stacks
55
Followers
132
Followers
325
Votes
2
Votes
12
Pros & Cons
Pros
  • 1
    Not as good as alternatives, good job security
  • 1
    Brings on-prem issues to the cloud
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
AWS IAM
Amazon CloudWatch
Amazon CloudWatch
ActiveMQ
ActiveMQ

What are some alternatives to NServiceBus, Amazon MQ?

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