Skip to main content
TrustRadius
Amazon SQS

Amazon SQS

Overview

What is Amazon SQS?

Amazon Web Services (AWS) Provides the Amazon Simple Queue Service (SQS), a managed message queue service which supports the safe decoupling and distribution of different components in a cloud infrastructure and cloud applications.

Read more
Recent Reviews

All Q's answered for SQS

7 out of 10
January 31, 2022
Our Application was integrated with third-party app, to fetch updated data from third-party app without keeping users to wait, we used SQS …
Continue reading
Read all reviews
Return to navigation

Pricing

View all pricing

All Data Transfer In

$0.00

Cloud
per GB

Standard Queue

$0.00000004

Cloud
per request

FIFO Queue

$0.00000005

Cloud
per request

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Details

What is Amazon SQS?

Amazon SQS Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(31)

Attribute Ratings

Reviews

(1-7 of 7)
Companies can't remove reviews or game the system. Here's why
January 31, 2022

All Q's answered for SQS

Score 7 out of 10
Vetted Review
Verified User
Our Application was integrated with third-party app, to fetch updated data from third-party app without keeping users to wait, we used SQS to bring data out of sync from users call. As user's request is sent to SQS queue and data is updated in our system.
  • 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
SQS will be helpful for usage in terms of creating a Async flow to your system with though high usage but not high importance data sent to SQS.Whereas in cases where we need to manage messages and auditing of them sent to SQS , also to monitor performance of system integrated with SQS , in such cases SQS would not be a preferred option.Best thing about SQS is that it is quite easy to implement and manage which makes it quick and hassle free.
August 03, 2021

My opinion about SQS !

Score 8 out of 10
Vetted Review
Verified User
Incentivized
SQS is one of AWS services we are using for many different projects.
It helps us to dissociate the components of our architectures and to create the best asynchronous processes possible
  • 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
SQS can be used when you need to create an architecture with asynchronous operations and when you are building many microservices that need to exchange messages.
It is different from SNS which allows you to broadcast messages to various targets
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Amazon SQS is being used by several teams internally for various functions. SQS works great in conjunction with Lambda and other AWS services to serve needs for both internal applications as well as customer facing applications.
  • 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.
If you are looking to build something that just requires a simple queue service (as the name implies) this is great for it. You might look elsewhere though if you get into more complicated needs. This is also very well suited if you are already using other services with AWS and intend to fully build whatever you are building in AWS. If you are looking for a mixed environment -- SQS is not for you.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Amazon Simple Queue Service (SQS) to manage even queues for several of our internal applications. We have an application that receives and processes jobs for ad placement on different advertising platforms. These jobs are relatively critical, and reliable processing is a must. Amazon Simple Queue Service (SQS) provides a serverless queue to handle these requests for us as well as a target that can be tracked to keep a job status as well as capture any errors executing the job.
  • 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).
While we use AmazonSimple Queue Service (SQS) in our serverless applications, it would be a great option to handle queue management for any internet-connect application. It provides the most benefit in situations where your application or service must maintain mission-critical queue of messages or jobs. If you're already using other AWS services you will find the greatest benefit.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
SQS service is under use at the company level, to handle the different application-level requirements. We mostly use it to decouple different level of modules so that we can provide an efficient solution to the end user.
  • 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.
We needed an application where we could communicate between asynchronous modules, and we needed a reliable solution where we could upload data under the HIPPA compliance, and Amazon SQS is the best fit.
January 26, 2019

It's a queue!

Gavin Hackeling | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use Amazon SQS to decouple and scale our micro-services. Some of our services are responsible for ingesting objects from external APIs. We then need to transform and store these objects. We use SQS to decouple the services responsible for ingestion and transformation. This allows us to easily scale either service tier; it also allows our developers to focus on just one responsibility. SQS is used only by the engineering team. It helps to improve developer velocity; our services have only one responsibility and are easy to reason about and test. It also helps us to inexpensively scale only some tiers in our system.
  • 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.
Amazon SQS is great for decoupling micro-services. Decoupling services can result in smaller services that are easier to understand and independently deployable, improving developer velocity. It is also easy to scale tiers independently. SQS is especially great if message order and exactly-once processing are not essential. If you have these requirements, you can still try FIFO queues, but their throughput is limited.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We used Amazon SQS primiarly as a service queue to perform asynchronous methods for Mandrill emails for customers. It was used by the Engineering team on behalf of the Marketing team.
  • 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
If you are trying to handle a large messaging queue to your customer base, specifically with email marketing notifications in mass quantities, this is a great tool. If you’re doing more personality, one-off messaging then this is not the ideal service.
Return to navigation