Amazon SQS OverviewUNIXBusinessApplication

Amazon SQS is the #3 ranked solution in top Message Queue Software. PeerSpot users give Amazon SQS an average rating of 7.8 out of 10. Amazon SQS is most commonly compared to Apache Kafka: Amazon SQS vs Apache Kafka. Amazon SQS is popular among the large enterprise segment, accounting for 71% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 22% of all views.
Buyer's Guide

Download the Message Queue (MQ) Software Buyer's Guide including reviews and more. Updated: January 2023

What is Amazon SQS?

Amazon Simple Queue Service (SQS) is a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications. SQS eliminates the complexity and overhead associated with managing and operating message oriented middleware, and empowers developers to focus on differentiating work. Using SQS, you can send, store, and receive messages between software components at any volume, without losing messages or requiring other services to be available. Get started with SQS in minutes using the AWS console, Command Line Interface or SDK of your choice, and three simple commands.

SQS offers two types of message queues. Standard queues offer maximum throughput, best-effort ordering, and at-least-once delivery. SQS FIFO queues are designed to guarantee that messages are processed exactly once, in the exact order that they are sent.

Amazon SQS Customers

EMS, NASA, BMW, Capital One

Amazon SQS Video

Amazon SQS Pricing Advice

What users are saying about Amazon SQS pricing:
  • "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."
  • "Amazon SQS is quite expensive and is at the highest price point compared to other solutions."
  • "Amazon SQS is more affordable compared to other solutions."
  • Amazon SQS Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Iaan Roux - PeerSpot reviewer
    Solutions Architect at a tech services company with 501-1,000 employees
    Real User
    Top 20
    Very resilient with numerous great features including a 256 kilobyte payload
    Pros and Cons
    • "The libraries that connect and manage the queues are rich in features."
    • "Be cautious around pay-as-you-use licensing as costs can become expensive."

    What is our primary use case?

    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.

    How has it helped my organization?

    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. 

    What is most valuable?

    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.

    What needs improvement?

    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.

    Buyer's Guide
    Message Queue (MQ) Software
    January 2023
    Find out what your peers are saying about Amazon, Apache, Oracle and others in Message Queue (MQ) Software. Updated: January 2023.
    670,523 professionals have used our research since 2012.

    For how long have I used the solution?

    I've been using this solution for a year. 

    How are customer service and support?

    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.

    Which solution did I use previously and why did I switch?

    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. 

    How was the initial setup?

    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. 

    What's my experience with pricing, setup cost, and licensing?

    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. 

    What other advice do I have?

    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. 

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Director at a tech vendor with 10,001+ employees
    Real User
    Top 5
    Simple to use and set up with good integration capabilities
    Pros and Cons
    • "I am able to find out what's going on very easily."
    • "It would be easier to have a dashboard that allows us to see everything and manage everything since we have so many queues."

    What is our primary use case?

    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. 

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    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.

    How are customer service and support?

    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. 

    How would you rate customer service and support?

    Neutral

    How was the initial setup?

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

    What about the implementation team?

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

    What's my experience with pricing, setup cost, and licensing?

    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. 

    What other advice do I have?

    We are a customer and an end-user. 

    I'd rate the solution eight out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Buyer's Guide
    Message Queue (MQ) Software
    January 2023
    Find out what your peers are saying about Amazon, Apache, Oracle and others in Message Queue (MQ) Software. Updated: January 2023.
    670,523 professionals have used our research since 2012.
    RahulSingh7 - PeerSpot reviewer
    Senior Software Developer at a manufacturing company with 1,001-5,000 employees
    Real User
    Top 5
    Stable, useful interface, and scales well
    Pros and Cons
    • "The most valuable feature of Amazon SQS is the interface."
    • "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."

    What is our primary use case?

    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.

    What is most valuable?

    The most valuable feature of Amazon SQS is the interface.

    For how long have I used the solution?

    I have been using Amazon SQS for approximately 

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

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

    How are customer service and support?

    I have not used the support from Amazon SQS.

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

    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.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Senior IT Architect (Architecture and Solutions Unit) at a tech services company with 1,001-5,000 employees
    Real User
    User-friendly, integrates well, but overall functionality could improve
    Pros and Cons
    • "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."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    I have been using Amazon SQS for approximately two years.

    What do I think about the stability of the solution?

    Amazon SQS is stable.

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

    What do I think about the scalability of the solution?

    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.

    How are customer service and support?

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

    What other advice do I have?

    I rate Amazon SQS a six out of ten.

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner / Integrator
    Flag as inappropriate
    PeerSpot user
    Director at Tibco
    Real User
    Top 5
    Send and receive messages across applications on a stable solution with no setup time
    Pros and Cons
    • "There is no setup just some easy configuration required."
    • "The solution is not available on-premises so that rules out any customers looking for the messaging solution on-premises."

    What is our primary use case?

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

    What is most valuable?

    Sending and receiving messages is the most valuable feature.

    What needs improvement?

    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.

    For how long have I used the solution?

    I have used the solution for a couple of years.

    What do I think about the stability of the solution?

    The solution is stable.

    What do I think about the scalability of the solution?

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

    How are customer service and support?

    The technical support is very good.

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    There is no setup just some easy configuration required.

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

    I give the solution a nine out of ten.

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

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Professor at Remo Engenharia
    Real User
    An affordable, easy-to-scale solution that is simple to deploy and maintain
    Pros and Cons
    • "The solution is easy to scale and cost-effective."
    • "I do not think that this solution is easy to use and the documentation of this solution has a lot of problems and can be improved in the next release. Most of the time, the images in the document are from older versions."

    What is our primary use case?

    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.

    What needs improvement?

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

    For how long have I used the solution?

    I have been using this solution for three years.

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    The solution is easy to scale and cost-effective.

    How was the initial setup?

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

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

    What other advice do I have?

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

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Buyer's Guide
    Download our free Message Queue (MQ) Software Report and find out what your peers are saying about Amazon, Apache, Oracle, and more!
    Updated: January 2023
    Product Categories
    Message Queue (MQ) Software
    Buyer's Guide
    Download our free Message Queue (MQ) Software Report and find out what your peers are saying about Amazon, Apache, Oracle, and more!