Amazon SQS vs MSMQ

Overview

Amazon SQS

Stacks2.8K

Followers2.0K

Votes171

MSMQ

Stacks33

Followers118

Votes3

Amazon SQS vs MSMQ: What are the differences?

Key Differences between Amazon SQS and MSMQ

Introduction

In this article, we will explore the key differences between Amazon Simple Queue Service (SQS) and Microsoft Message Queue (MSMQ).

Architecture and Management:
- Amazon SQS is a fully-managed service provided by AWS, which means that the infrastructure and maintenance tasks are handled by AWS. It utilizes a distributed architecture to ensure high availability and fault tolerance.
- MSMQ, on the other hand, is a software-based application that needs to be installed and managed on a server. It relies on the server's resources for its functioning and does not provide built-in high availability or fault tolerance features.
Messaging Patterns:
- Amazon SQS supports both standard and FIFO (First-In-First-Out) messaging patterns, giving developers the flexibility to choose the most appropriate pattern for their use case. FIFO queues ensure that the order in which messages are sent and received is strictly preserved.
- MSMQ only supports the standard messaging pattern, where messages are delivered in a best-effort manner without any guarantees on ordering or message delivery.
Scalability and Throughput:
- Amazon SQS is designed to handle a virtually unlimited number of messages and offers high throughput capabilities. It automatically scales based on the workload and can handle bursty traffic patterns effectively.
- MSMQ has limitations on scalability and throughput, as it relies on the resources of the server it is installed on. It may require additional capacity planning and configuration to handle increased workloads.
Message Size and Visibility Timeout:
- Amazon SQS allows messages of up to 256 KB in size. It also provides a visibility timeout feature, which allows a message to be temporarily invisible to other consumers after it has been fetched from the queue, preventing multiple consumers from processing the same message concurrently.
- MSMQ has a message size limit of 4 MB and does not include a built-in visibility timeout mechanism. Developers need to implement custom logic to handle message visibility and preventing duplicate processing.
Integration with Serverless and Event-Driven Architectures:
- Amazon SQS is seamlessly integrated with various AWS services, making it a suitable choice for serverless and event-driven architectures. It can be easily integrated with AWS Lambda, Amazon SNS, and other services to build scalable and event-driven systems.
- MSMQ is primarily designed for use within on-premises Windows environments and does not offer native integration with cloud-based serverless architectures. It may require additional integration efforts to integrate with cloud-based services.
Pricing Models:
- Amazon SQS pricing is based on the number of requests made, the message data size, and additional features like dead-letter queues. It offers a pay-as-you-go model, allowing users to pay only for the resources they consume.
- MSMQ is a part of the Windows operating system and does not have separate pricing. However, the cost of managing and maintaining the underlying server infrastructure needs to be considered.

In summary, Amazon SQS is a fully-managed, scalable, and highly available messaging service with support for various messaging patterns and seamless integration with cloud services. MSMQ, on the other hand, is a software-based application that needs to be managed and may have limitations on scalability and integration with cloud-based architectures.

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 Amazon SQS, MSMQ

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

Amazon SQS	MSMQ
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.	This technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. Applications send messages to queues and read messages from queues.
A queue can be created in any region.;The message payload can contain up to 256KB of text in any format. Each 64KB ‘chunk’ of payload is billed as 1 request. For example, a single API call with a 256KB payload will be billed as four requests.;Messages can be sent, received or deleted in batches of up to 10 messages or 256KB. Batches cost the same amount as single messages, meaning SQS can be even more cost effective for customers that use batching.;Long polling reduces extraneous polling to help you minimize cost while receiving new messages as quickly as possible. When your queue is empty, long-poll requests wait up to 20 seconds for the next message to arrive. Long poll requests cost the same amount as regular requests.;Messages can be retained in queues for up to 14 days.;Messages can be sent and read simultaneously.;Developers can get started with Amazon SQS by using only five APIs: CreateQueue, SendMessage, ReceiveMessage, ChangeMessageVisibility, and DeleteMessage. Additional APIs are available to provide advanced functionality.	-
Statistics
Stacks 2.8K	Stacks 33
Followers 2.0K	Followers 118
Votes 171	Votes 3
Pros & Cons
Pros 62 Easy to use, reliable 40 Low cost 28 Simple 14 Doesn't need to maintain it 8 It is Serverless Cons 2 Has a max message size (currently 256K) 2 Proprietary 2 Difficult to configure 1 Has a maximum 15 minutes of delayed messages only	Pros 2 Easy to learn 1 Cloud not needed Cons 1 Windows dependency

What are some alternatives to Amazon SQS, MSMQ?

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.

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.

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

Amazon SQS vs MSMQ: What are the differences?

Key Differences between Amazon SQS and MSMQ

Introduction

In this article, we will explore the key differences between Amazon Simple Queue Service (SQS) and Microsoft Message Queue (MSMQ).

Architecture and Management:
- Amazon SQS is a fully-managed service provided by AWS, which means that the infrastructure and maintenance tasks are handled by AWS. It utilizes a distributed architecture to ensure high availability and fault tolerance.
- MSMQ, on the other hand, is a software-based application that needs to be installed and managed on a server. It relies on the server's resources for its functioning and does not provide built-in high availability or fault tolerance features.
Messaging Patterns:
- Amazon SQS supports both standard and FIFO (First-In-First-Out) messaging patterns, giving developers the flexibility to choose the most appropriate pattern for their use case. FIFO queues ensure that the order in which messages are sent and received is strictly preserved.
- MSMQ only supports the standard messaging pattern, where messages are delivered in a best-effort manner without any guarantees on ordering or message delivery.
Scalability and Throughput:
- Amazon SQS is designed to handle a virtually unlimited number of messages and offers high throughput capabilities. It automatically scales based on the workload and can handle bursty traffic patterns effectively.
- MSMQ has limitations on scalability and throughput, as it relies on the resources of the server it is installed on. It may require additional capacity planning and configuration to handle increased workloads.
Message Size and Visibility Timeout:
- Amazon SQS allows messages of up to 256 KB in size. It also provides a visibility timeout feature, which allows a message to be temporarily invisible to other consumers after it has been fetched from the queue, preventing multiple consumers from processing the same message concurrently.
- MSMQ has a message size limit of 4 MB and does not include a built-in visibility timeout mechanism. Developers need to implement custom logic to handle message visibility and preventing duplicate processing.
Integration with Serverless and Event-Driven Architectures:
- Amazon SQS is seamlessly integrated with various AWS services, making it a suitable choice for serverless and event-driven architectures. It can be easily integrated with AWS Lambda, Amazon SNS, and other services to build scalable and event-driven systems.
- MSMQ is primarily designed for use within on-premises Windows environments and does not offer native integration with cloud-based serverless architectures. It may require additional integration efforts to integrate with cloud-based services.
Pricing Models:
- Amazon SQS pricing is based on the number of requests made, the message data size, and additional features like dead-letter queues. It offers a pay-as-you-go model, allowing users to pay only for the resources they consume.
- MSMQ is a part of the Windows operating system and does not have separate pricing. However, the cost of managing and maintaining the underlying server infrastructure needs to be considered.

Amazon SQS vs MSMQ

Overview

Amazon SQS vs MSMQ: What are the differences?