Amazon SQS Reviews

The tool I use to transform and move data can read the entries from Amazon SQS. For example, to start some workflow orchestration, it checks Amazon SQS, reads new messages from it, and then runs some transformation. My responsibility was setting up the new SQS, setting up the right policies, adding some text, and allowing communication.

It's very quick and easy to build or set up Amazon SQS. It's a very stable solution, and we have never faced any downtime issues.

Sending or receiving messages takes some time, and it could be quicker.

I have been using Amazon SQS for one year.

I rate the solution ten out of ten for stability.

Around 500 users are using the solution in our organization.

I rate Amazon SQS ten out of ten for scalability.

The solution’s initial setup is straightforward.

Beginners can very easily set up Amazon SQS. It requires just a few clicks and then some permissions. The solution can be installed in 15 minutes.

Amazon SQS is moderately priced.

Users need to check the number of messages. Since the solution works on a pay-as-you-go model, it could be expensive if the number of messages is very large.

Overall, I rate Amazon SQS a nine out of ten.

The tool helps to process events in a microservices cluster. We use it in the financial industry. 

I like how we can subscribe to multiple topics in Amazon SQS. It's also much simpler and quicker to set up than other solutions. It also supports patterns like Kafka and RapidMQ's fan-out pattern but with easier implementation.

Amazon SQS is costly. I think there could be improvements in how it facilitates comparisons between different AWS products. A calculator would be helpful. The calculator for Kafka is based on factors like throughput or storage used in the last month. In contrast, the calculator for Amazon SQS is based on the number of transactions processed. These different approaches make it challenging to compare them directly. I suggest AWS provide a straightforward calculator where I can input one aspect, and it calculates costs for multiple solutions. 

I have been working with the product for two years. 

I rate the product's stability a ten out of ten. 

I rate the solution's scalability a ten out of ten. My company has 100 users. 

I rate the solution's deployment ease an eight out of ten. Its deployment is generally quick, but it involves considerations around security, which are essential for DevOps teams. Typically, it takes about one week for deployment. However, if I handled it for my project personally, the deployment time would likely be shorter.

I rate the tool's pricing a nine out of ten. 

We manage and monitor our Amazon SQS performance and costs using DataOps. It helps us with intuitive data. Transitioning from our legacy tools to Amazon SQS would be beneficial because it's simple to set up and can serve as a pilot for our approach.

I rate the overall product an eight out of ten. 

We use it for event-driven messaging and workflows.

We use SNS as the publisher, and our procurement service subscribes to those events using SQS.

In the past, we relied on time-based or batch-based processes to send data between services on-premises. With SQS, we can trigger actions based on real-time changes in business processes, improving reliability.

Moreover, SQS can grow with our needs.

SQS message delay feature and redundant retention policies helped us to avoid replaying events due to errors and ensure our messages are processed reliably.

We use CloudWatch for monitoring.

It's easy to implement and cost-effective.

The visibility timeout feature is very nice. We use the visibility timeout in our internal processes to ensure that if a message fails to process, it becomes available for other consumers after a set period.

The current visibility timeout of five minutes is okay. However, I'd like to explore the possibility of extending it for specific use cases.

I have been using it for five to six years now. We (my company) use SQS quite extensively, and it has been quite a good service till now.

It is a stable product.

It is a scalable product. We can handle 10,000 events easily. 

We have a lot of end users using it in my company. We have around 2,000 end users using it. We have multiple locations. 

I have used RabbitMQ. 

The initial setup is very straightforward. It's a simple checkbox-kinda process. 

It is not difficult to maintain it. It is very easy. Overall, it is a very straightforward solution. 

It does a very good job. The cost was the main issue for us.

It's quite expensive. 

It's a great solution. I would recommend using it. 

Overall, I would rate the solution a nine out of ten. I've used it, and it seems to be a solid solution.

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.

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.

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.

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.

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.