Filter Ratings and Reviews
Filter 15 vetted Amazon SQS reviews and ratings
Reviews (1-5 of 5)
Companies can't remove reviews or game the system. Here's why.
February 20, 2020
Amazon Simple Queue Service (SQS) - Easy because it's there
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.
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).
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 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.
January 23, 2019
SQS is my Queue service of choice!
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
Amazon SQS Scorecard Summary
About 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.
Categories: Message Queue
Amazon SQS Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |