Amazon SQS Reviews

As an IT company, we develop various solutions and products for our clients. This particular item is utilized as a component of a comprehensive solution for specific customer needs across various industries.

Amazon SQS is not a complex solution, we mainly use it for its primary purpose. It's an integral part of our application's workflow.

I appreciate that Amazon SQS is fully integrated with Amazon and can be accessed through normal functions or serverless functions, making it very user-friendly. Additionally, the features are comparable to those of other solutions.

As a company that uses IBM solutions, it's difficult to compare Amazon SQS to other solutions. We have been using IBM solutions for a long time and they are very mature in integration and queuing. In my role as an integration manager, I can say that Amazon SQS is designed primarily for use within the Amazon ecosystem and does not have the same level of functionality as IBM MQ or other similar products. It has limited connectivity options and does not easily integrate with legacy systems.

I have been using Amazon SQS for approximately two years.

Amazon SQS is stable.

I rate the stability of Amazon SQS a nine out of ten.

Amazon SQS is scalable. It is not suitable for many use cases. It is suitable for cloud applications but it's not suitable for on-premises or hybrid.

I rate the scalability of Amazon SQS a seven out of ten.

The components are simple in Amazon SQS. The components are not complex to need support. I did not use the support.

I rate Amazon SQS a six out of ten.

This is an event-driven solution so messages go through the API gateway onto the queue and are then processed from there. We are customers of Amazon.

The biggest improvement we've seen from SQS is that our backing system is not under strain anymore and messages don't get lost because the queue is now very resilient. If our backing process goes down, the messages remain in the queue. 

There are several valuable features that SQS offers including the standard queue, the AWS interface and the quality documentation provided by AWS. The libraries that connect and manage the queues are rich in features. The visibility of the messages is great and the 256 kilobytes payload is also good. SQS improves the scalability and resilience of the solution. It's also very simple and very straightforward.

If you require event-driven development, there might be advanced queuing requirements that SQS can't offer. I don't think it supports transactions although I'm no expert around that. The biggest issue is likely to be cost estimations because you might get a huge bill if you're not careful.

I've been using this solution for a year. 

The documentation is very good so we've never had to reach out to the SQS technical support team. There's a very rich source of information around SQS.

We initially used Rabbit MQ. SQS is our first attempt at event-driven, asynchronous development. We chose to migrate our infrastructure to AWS and took on the native queuing solution that AWS supplies. It was an opportunity for us and the learning curve to get going with SQS is very low. 

Another reason we went with SQS is the zero maintenance from our point of view. The service is hosted by AWS and doesn't require IT support. 

The initial setup was reasonably straightforward. We deployed in-house and used one engineer for the process. SQS is a managed service by AWS so they carry out the maintenance. Once the solution is running, it gets used by clients who interact with the APIs. In terms of developers we have five users but the system that uses it has billions of users with accounts that get managed through SQS. To date, we've implemented it in two of our in-house projects and there will likely be more. 

Part of the reason we went for SQS is that it's a pay-as-you-use licensing model. 
In addition, they offer a significant amount of free monthly transactions before you start paying. It's possible that down the line SQS will become too expensive and we may need to look for an alternative. 

I would definitely suggest carrying out cost estimations prior to purchase because if you need it for a very high number of requests per month, the costs might be significantly higher and not worth it. In that event, it may be worth looking at ActiveMQ or RabbitMQ, where you can better control licensing costs. That said, this is a very good solution for us.

I rate this solution eight out of 10. 

The primary use case of this solution is to send and receive messages across applications.

Sending and receiving messages is the most valuable feature.

The solution is not available on-premises so that rules out any customers looking for the messaging solution on-premises. The price is on the high end and has room for improvement.

I have used the solution for a couple of years.

The solution is stable.

To the extent necessary, we have been able to scale the solution. We have less than 100 people using the solution.

The technical support is very good.

Positive

There is no setup just some easy configuration required.

The licensing cost is publicly available on the AWS page. Amazon SQS is quite expensive and is at the highest price point compared to other solutions.

The price is based on the number of messages sent and received.

I give the solution a nine out of ten.

For people who don't want any infrastructure and managing overhead, I recommend Amazon SQS.

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.

The primary use case of this solution is for collecting event data for analytic purposes.

In our case, when a user selects a function in our app, the information is collected. Analytics is performed on the data to determine the functionalities that clients use the most. 

Additionally, the data can tell us the most popular service demands such that resources can be assigned accordingly.

Documentation of this solution can be improved. Sometimes, the images in the document are from older versions.
 

I have been using this solution for three years.

We have never had a problem with the stability of the solution.

The solution is easy to scale and cost-effective.

The profile management of this solution is difficult to set up. 

However, after the initial setup, it is easy to deploy, maintain, and test.

The security of a cloud solution is very important and attention must be given to profile management, key generation, and key protection.

SQS is very stable, and it has lots of features.

There are some issues with SQS's transaction queue regarding knowing if something has been received.

SQS is very stable.

Amazon's technical support could be more responsive.

Neutral

SQS's pricing is very good - I would rate it nine out of ten.

I would give SQS a rating of nine out of ten.