Overview

Amazon SQS

Stacks2.8K

Followers2.0K

Votes171

WCF

Stacks125

Followers107

Votes5

Amazon SQS vs WCF: What are the differences?

Introduction:

Message Delivery Model: Amazon SQS operates on a pull-based message delivery model where consumers have to actively request messages from the queue, whereas WCF supports both push and pull message delivery models, allowing for more flexibility in message handling.
Scalability: Amazon SQS is highly scalable and can handle an unlimited number of messages, making it suitable for large-scale applications with varying message loads. In contrast, WCF may require additional configuration and infrastructure to achieve similar scalability.
Managed Service: Amazon SQS is a fully managed service provided by AWS, which takes care of underlying infrastructure, scaling, and maintenance, while WCF requires more manual configuration and management, especially in on-premises environments.
Protocol Support: Amazon SQS supports multiple protocols such as HTTP, HTTPS, and Amazon SDKs for different programming languages, enabling seamless integration with various applications. WCF, on the other hand, primarily relies on SOAP-based messaging, which may limit interoperability with non-WCF systems.
Cross-Platform Compatibility: Amazon SQS can be easily used across different platforms and environments, thanks to its cloud-based nature, whereas WCF is more suitable for Windows-based systems and may require additional setup for cross-platform compatibility.
Pricing Model: Amazon SQS operates on a pay-as-you-go pricing model based on usage, while WCF is typically offered as part of the Windows Server package or Visual Studio subscriptions, making it more cost-effective for certain enterprise setups.

In Summary, Amazon SQS and WCF differ in message delivery model, scalability, managed service aspect, protocol support, cross-platform compatibility, and pricing model.

🔥 Trending in Background Jobs on StackShare

Solid Queue Background Jobs

Database-backed active job backend

Try it View Docs Alternatives

Try

0

1

Advice on Amazon SQS, WCF

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	WCF
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.	It is a framework for building service-oriented applications. Using this, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application.
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 125
Followers 2.0K	Followers 107
Votes 171	Votes 5
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 Difficult to configure 2 Proprietary 1 Has a maximum 15 minutes of delayed messages only	Pros 5 Classes

What are some alternatives to Amazon SQS, WCF?

Firebase

Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.

Socket.IO

It enables real-time bidirectional event-based communication. It works on every platform, browser or device, focusing equally on reliability and speed.

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.

PubNub

PubNub makes it easy for you to add real-time capabilities to your apps, without worrying about the infrastructure. Build apps that allow your users to engage in real-time across mobile, browser, desktop and server.

Pusher

Pusher is the category leader in delightful APIs for app developers building communication and collaboration features.

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.

SignalR

SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization.

Ably

Ably offers WebSockets, stream resume, history, presence, and managed third-party integrations to make it simple to build, extend, and deliver digital realtime experiences at scale.