Amazon SQS

Dead letter queue for failed messages

Queue management

Message delivery to listener

More frequest polling will be expensive

No detailed monitoring of queues, just current data and regular monitoring is present

No way to fetch messages back from the queue

Very nice SDK

Useful console

Easy to use

Sometime the information (in-flight messages for instance) displayed in the console are not up-date

You need to be aware of how your queues are used to avoid cost issues

Simple to start: SQS is simple to get started with and configure if you are new to using both AWS and if you are new to using this particular service.

Pricing: Pricing for SQS is surprisingly less complicated than other services in AWS and is pretty reasonable.

Might not be the best solution if you aren't "all in" with AWS: Many AWS services rope you in to being all in with AWS. It becomes pretty difficult to implement full solutions using AWS without using their entire stack. SQS is not really any different in that respect.

There are free services that can do the same/similar things to SQS that may make it easier to implement outside AWS, or at least in part outside of AWS.

It provides an always-available serverless queue for workflows or mission-critical processes.

Is extremely low cost and overall costs to our environments have been negligible.

Scheduling options could be a bit more robust since deferred deliveries can be held for a maximum of 15 minutes currently.

Maximum message size limitations are not a huge hassle, but it would be nice to have the option to include larger messages with detailed log messages. This can be worked around but requires using another service such as DynamoDB to persist large messages and reference them from Amazon Simple Queue Service (SQS).

Provides very good support for asynchronous processes.

Hosted in the cloud, which supports HIPPA complaints.

Options for a FIFO and Standard queue, so anyone can choose on the base of their requirements.

Has an add-on functionality of configurable parameters, like Delivery Delay, Default Visibility Timeout, Message Retention Period, Receive Message Wait Time, etc.

Almost all of the functionality has been covered by SQS, but they could improve the throughput time.

Also, they could provide built-in Cloud Watch, so that we can easily configure it without any external efforts.

SQS is reliable and fully managed. Our engineers do not have to worry about running RabbitMQ.

SQS is very inexpensive.

SQS allows data to be encrypted in transit, which may be required for compliance in some products.

FIFO queues provide exactly-once processing.

Lambda integration is lacking. It would be great if enqueueing a message could trigger a Lambda function. Today, Lambda functions can be invoked periodically by CloudWatch and poll SQS for messages.

FIFO queue throughput is limited to ~300 messages/second. This was not a problem for us, but it may be for larger organizations.

Delay queues can be great for implementing notification features, but the maximum delay period is too short.

Background messaging queue service

Easy to setup and get up and running

Great user interface to notify you of a message getting stuck

Email messages to inform you of why a message got stuck

SMS notification for stuck messages

Better error handling