Amazon SQS Reviews

We use Amazon SQS for an asynchronous solution. We receive data through API calls, which we process and log to our database. To avoid doing this during the API call, we offload it to Amazon SQS. We have a service that monitors Amazon SQS to process the data in the background.

It helps with high volumes of data on the API, preventing us from doing too much processing for every API call. By using Amazon SQS as a holding area, we process data in the background, which does not affect the user experience on the front end.

Amazon SQS is reliable, with no issues to date. It handles its load well, and the graphs for monitoring are good. It offers durable storage, reducing data loss. The messages remain until processed and deleted, with a retention period of a maximum of 14 days.

It would be beneficial to have the ability to peek at messages currently in Amazon SQS without needing to monitor incoming messages. Additionally, when using Azure, I could look at messages while they were there. Such a feature would be useful in Amazon SQS as well.

I have used Amazon SQS for about two years now.

Amazon SQS is stable and handles its load effectively.

While Amazon SQS itself is not scalable, it supports scalability. It acts as a holding area between high volumes of messages, allowing us to scale and receive more messages without worrying about whether Amazon SQS can handle it.

I have not needed to escalate any issues to Amazon SQS customer support. It has been reliable without any need for assistance.

Positive

I have used Azure queues and Azure services. Azure allowed me to see the messages in the queue, which I found beneficial. However, Amazon SQS can store more messages at a time than Azure.

The initial setup was fairly straightforward.

From a programming and reliability standpoint, Amazon SQS is a good part of the infrastructure. It saves a lot of headaches and helps maintain system integrity.

The pricing and licensing details are abstracted from me, so I have not looked into them.

I have considered Azure queues and Azure services.

Using queues in an infrastructure is a good idea for certain scenarios. If you're going to use AWS and need queues, then Amazon SQS is the solution. I would recommend its use if you have simple enough needs.

I'd rate the solution eight out of ten.

Amazon SQS is basically a queue service. Each message is treated as an event and added to a container. When a message needs to be processed, a trigger can be set.

One of the useful features is the ability to schedule a call after a certain number of messages accumulate in the container. For example, if there are ten messages in the container, you can perform a specific action.

Recently, I encountered an issue where I couldn't send a message to multiple recipients. If two subscribers are subscribed to the same channel, the message can only be sent to either one of them, not both. I believe this is an area that needs improvement.

So, I cannot send a message to multiple people simultaneously. It can only be sent to one recipient.

I've been using Amazon SQS for about six months.

Amazon SQS is not very stable. 

It does not that stable because you can't deliver the same message to two people; how can you add that feature on the AWS. So we have the option to add multiple subscribers to the same message, but it's not delivering this message to all the people at the same instant.

Amazon SQS is a scalable product. There are 30 people using Amazon SQS in our company.

Amazon SQS was easy to set up.

If you only have one job to run, I would recommend using it. However, if you need to handle multiple jobs, I would not recommend it.

Overall, I would rate the solution a five out of ten. Since it doesn't support sending the same message to multiple subscribers, it lacks usefulness in certain cases.

We used SQS for the Kapolei system to ensure that certain tasks were executed precisely once. The first-in, first-out (FIFO) capability was a great feature for us. Additionally, its redundancy out of the box meant we didn't have to worry about missing messages. It provided peace of mind and automatically instilled trust, relieving us of any concerns.

When you have millions of messages, it can get quite tender. Initially, Amazon SQS's maximum payload size wasn't sufficient for our needs. However, we found a workaround by splitting the payload into smaller chunks and only providing the URL within the SQL structure.

I have been using Amazon SQS for five years.

I rate the solution’s stability a nine out of ten.

The solution is scalable, so we didn't need to care about it. We encountered no glitches or bugs.

I rate the solution’s scalability a ten out of ten.

We were utilizing business support, which is relatively costly compared to other vendors. However, each time we reached out, the service was quite satisfactory.

Positive

The solution is easy to deploy and to configure. The implementation, including our application side, takes less than four hours. It was really quick.

The installation was handled by one person. That one person spent four hours working on it. We had prior knowledge of SQS. So, it was about trusting the installation and configuration process rather than figuring out how the system releases.

I rate the initial setup a ten out of ten, where one is difficult, and ten is easy.

The solution has a monthly subscription, which costs around 22 dollars.

One person is enough for the solution's maintenance.

We don't have to maintain our tooling system, which was quite flaky. We had problems with high availability, and when we covered the below balance of the Reddit cluster, we sometimes encountered cases where the job was executed twice.

Overall, I rate the solution a ten out of ten.

Generally, we use it for asynchronous communication. We have actively utilized it for the past three years. Basically, we use it to exchange events and messages when we need communication and integration in our architecture.

Amazon SQS has provided us with a better experience, better performance, and better communication in our scenario. It is a valuable tool for our needs.

There are many valuable features, such as resuming messages, high performance, first-in-first-out (FIFO) capability, message grouping, and integration with AWS Key Management Service (KMS). With SQS, we can trigger events in various cloud environments. It offers numerous benefits for us.

There is room for improvement in the performance system.  Sometimes, we have to switch to another component similar to SQS because the patching tool for SQS is relatively slow for us. 

Recently, we had a necessity for encryption and a stronger security strategy. We faced difficulties in providing this with scalability. So, I'm not sure about the specific feature. There are good and new features related to security, secret chaining, and threat security that can be improved in the future for our clients and close customers.

I have been using Amazon SQS for more than three years. I use the latest version. 

It's very stable.

Amazon SQS is a scalable solution. We have specific needs for this product currently. Generally, we are working with big data size, and Amazon SQS provides stability and the necessary features for our data reports.

So, in the future, we will continue using it in our factory and as part of our in-house solution.

The technical support is very good. We have an enterprise support model, so when we raise a ticket, we receive feedback within one hour and thirty minutes.

It is worth the investment. Generally, it's more expensive. For example, in the cloud, the initial setup may be more expensive in size and investment, but the returns are better for us. 

But, it depends on the specific case, you know, like starting small and configuring the services according to your needs. It's better for us in the cloud but varies depending on the situation.

The pricing model is pay-as-you-use. It depends on your usage and configuration. But generally, it's better. The cost benefits are better for us.

I would definitely recommend using the solution. Overall, I would rate the solution a nine out of ten.

We have recently started using Amazon SQS and we are in the R&D phase. We want to see how resilient the solution is. We use Amazon SQS for integration purposes between our different applications.

The most valuable feature of Amazon SQS is the interface.

I have been using Amazon SQS for approximately 

Amazon SQS is stable from the usage that we have had so far.

The scalability of the solution is good. We can scale it to different regions and deploy it within Amazon AWS.

I have not used the support from Amazon SQS.

We previously were using ActiveMQ and we had to manage it manually on our on-premise server.  We have seen that a lot of times the messaging queuing service stopped responding or we had to restart the server or the services themselves on the server. This is the reason we are switching to Amazon SQS.

Amazon SQS is well integrated with Amazon AWS which is helpful if it is needed to be scaled. ActiveMQ is open-source and free to use but it is not resilient or dependable. It stops working at times and you have to manage the server yourself. Amazon SQS is serverless, you don't have to manage the server, you only have to manage the permissions.

The initial setup of Amazon SQS is in the middle range of difficulty. You need to learn Amazon AWS and know how to navigate, create resources, and structures, and provide rules.

The pricing of Amazon SQS is reasonable. The first million requests are free every month, and after, it's cost 40 cents for every million requests. There are not any additional fees.

This is a free-to-use solution for somebody who wants to do 1 million requests, and this is sufficient for any application at a small organization. It's cost-effective, reliable, and easily scalable.

I rate Amazon SQS an eight out of ten.

I use Amazon SQS for notification services.

It allows for easier management of notifications as it serves as a listener with various protocols like HTTPS.

Amazon SQS provides faster search through indexing via OpenSearch.

Packages sometimes have delays in dropping, indicating reliability issues.

I have been using it whenever a notification service was needed, which is approximately six and a half years.

There are occasional reliability issues where packages are delayed.

There is a need for better congestion tools, and Kafka is suggested as an alternative in the market today.

I have never contacted their support team.

Neutral

I was a developer, so we never contacted the support team directly.

I don't know about pricing.

Kafka is used a lot in the market today for notification services.

AWS subscription includes the deployment of the tool along with other services, making it comprehensive under one device.

I'd rate the solution seven out of ten.

It's a streaming application. For example, it is basically an autonomous vehicle solution for the case management side. It gives alerts and we have devices that will connect to IoT and the other service processes to provide data and then put it in a queue. 

The solution is simple to use. I like it. I don't need to do too many things. However, it is basically dependent on the vendor configuration.

It can really integrate with any other telemetry angle. It can integrate with CloudWatch and CloudWatch is configured with AWS. 

I am able to find out what's going on very easily.

The initial setup was easy.

Their telemetry could be better. Whene we see something going wrong, we need to find out the telemetry separately. That's fine if it's just one case, however, if we have 100 services and have many queues to manage and you need to understand what's going on in your system, there are not enough tools that are available. We have to move all data and then go through a service vendor. It would be easier to have a dashboard that allows us to see everything and manage everything since we have so many queues. We need to have more power to observe all that's happening. We need to rely on plugins to assist. 

The solution needs to be more of an all-in-one solution.

I've used the solution for the last three years. 

While the solution is stable, based on my long stint in IT my experience is that anything can be improved.

The solution can scale. However, you need to find your requirements to see what is being consumed or reduced to see if there are limitations you can address via configuration. 

We have 300 people using the solution. We use it daily. It is integrated with part of our overall solution.

The support hasn't been ideal. It could be better. They need better response times. Also, sometimes we deal with people who are not extremely knowledgeable. However, it is case by case. They are not consistent. There are other cloud providers that ultimately offer better services. 

Neutral

The solution is easy to implement. I'd rate it a four out of five in terms of the ease of setup. 

The setup was handled in-house. We didn't need any outside support. We have our own team that can handle it. 

A separate team handles licensing. I can't speak to any pricing. However, my understanding is that the solution is moderately priced. It's rather competitive. 

We are a customer and an end-user. 

I'd rate the solution eight out of ten.

We use the service in cloud-native event-driven integrations.

The service needs more user-friendly discoverability for self-service scenarios.

The product is stable.

I would rate the tool's scalability an eight out of ten.

The product's setup is simple. We can speed up the deployment and complete it in a few minutes if we have an AWS contract. 

I would rate the product a nine out of ten. If you are using the AWS platform, then you will find a lot of use cases for the solution.