No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon SQS vs Redis comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

ROI

Sentiment score
6.8
Amazon SQS enhances performance and reliability, increasing productivity by reducing programming effort and labor costs, despite initial investment.
Sentiment score
7.3
Redis boosts performance and reduces costs, enhancing API latency and productivity while allowing focus on feature development.
Using Amazon SQS has led to increased productivity and reduced man-hour costs.
IT Specialist at a financial services firm with 51-200 employees
We reduced the database read load by around 30 to 40 percent and improved API response time by 20 to 30 percent, specifically for frequently accessed endpoints.
SDE 2 at Virtusa
We have seen a positive return on investment from using Redis, mainly through improved application performance, reduced database load, and lower operational overhead.
Senior Software Engineer at a consultancy with 1-10 employees
 

Customer Service

Sentiment score
6.7
Amazon SQS customer service satisfaction varies, influenced by purchased support level, with premium options offering improved experiences.
Sentiment score
6.4
Redis users rarely need support due to stability, relying on documentation and community, with mixed experiences reported.
They meet their tasks effectively.
IT Specialist at a financial services firm with 51-200 employees
By simply referring to their documentation, we have been able to fix our bugs and general issues.
Senior Software Engineer at a consultancy with 1-10 employees
Since Redis is quite stable and well-documented, we have not needed much support, but when required, the response has been helpful.
SDE 2 at Virtusa
 

Scalability Issues

Sentiment score
8.1
Amazon SQS excels in scalability and integration, though users note configuration needs and potential message duplicates.
Sentiment score
7.8
Redis excels in scalability and efficiency, handling high traffic with clustering and sharding, benefiting enterprise application demands.
Amazon SQS is highly scalable, automatically managing itself based on the load.
IT Specialist at a financial services firm with 51-200 employees
I can easily scale up or down with Amazon SQS without any issues.
Senior Data & AI Engineer at Imprint
The in-memory architecture provides consistently low-latency access even as data access patterns and request volume increase.
Senior Software Engineer at a consultancy with 1-10 employees
Data migration and changes to application-side configurations are challenging due to the lack of automatic migration tools in a non-clustered legacy system.
Data Engineer at a photography company with 1,001-5,000 employees
With features such as clustering and replication, it can handle high traffic and a large database very effectively.
SDE 2 at Virtusa
 

Stability Issues

Sentiment score
8.3
Users highly trust Amazon SQS for its stability, reliability, and performance, often preferring it over RabbitMQ and Kafka.
Sentiment score
7.9
Redis is lauded for its stability, reliable caching performance, and robust architecture, supported by strong community and managed services.
With Amazon SQS, such maintenance is not needed, making it more reliable and secure.
IT Specialist at a financial services firm with 51-200 employees
The stability of Amazon SQS is very good, as I find it to be very stable.
Senior Data & AI Engineer at Imprint
Redis has consistently provided fast and predictable performance, particularly for caching and high-frequency data access scenarios.
Senior Software Engineer at a consultancy with 1-10 employees
Redis is fairly stable.
Data Engineer at a photography company with 1,001-5,000 employees
 

Room For Improvement

Amazon SQS users seek better documentation, integrations, security, pricing, UI, performance, message handling, and monitoring tools.
Redis users seek improvements in cache management, user interface, observability, scalability, security setup, and cloud integrations for enhanced usability.
It would be beneficial if there was a provision to configure and retain messages for longer than a week.
IT Specialist at a financial services firm with 51-200 employees
Making security features and enterprise governance capabilities easier to configure out of the box would help organizations adopt Redis more confidently for larger and more critical workloads.
Senior Software Engineer at a consultancy with 1-10 employees
Data persistence and recovery face issues with compatibility across major versions, making upgrades possible but downgrades not active.
Data Engineer at a photography company with 1,001-5,000 employees
Redis itself does not enforce consistency with the primary database, so developers need to carefully design cache invalidation strategies.
Software Engineer at ValueMomentum
 

Setup Cost

Amazon SQS offers a cost-effective pay-as-you-use model, but high-scale usage can increase costs compared to alternatives.
Enterprise Redis costs vary by deployment model, with self-managed being cost-effective and cloud services charging for memory usage.
On a scale of one to ten, where one is very cheap, I would rate the pricing as one.
IT Specialist at a financial services firm with 51-200 employees
The main value comes from the performance improvements, reduced database load, and increased scalability that Redis provides.
Senior Software Engineer at a consultancy with 1-10 employees
Since we use an open-source version of Redis, we do not experience any setup costs or licensing expenses.
Data Engineer at a photography company with 1,001-5,000 employees
The pricing is reasonable for the performance provided.
SDE 2 at Virtusa
 

Valuable Features

Amazon SQS enables scalable, reliable messaging with easy AWS integration, supporting FIFO and standard queues for efficient processing.
Redis is preferred for speed and reliability, offering low latency, high throughput, and efficient scaling with minimal configuration.
If there's a failure in the system after consuming a message, SQS's settings ensure the message is not deleted until confirmation.
IT Specialist at a financial services firm with 51-200 employees
If we compare with other solutions such as RabbitMQ for messaging, Amazon SQS is easier to use and easier to create the queue.
Senior Data & AI Engineer at Imprint
It functions similarly to a foundational building block in a larger system, enabling native integration and high functionality in core data processes.
Data Engineer at a photography company with 1,001-5,000 employees
First is its in-memory preference, as Redis is extremely fast, making it ideal for caching and session management where low latency is critical.
Software Engineer at ValueMomentum
By offloading frequent reads from the database and enabling fast in-memory cache access, it reduced latency, improved throughput, and helped maintain stability during peak loads.
SDE 2 at Virtusa
 

Categories and Ranking

Amazon SQS
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
31
Ranking in other categories
Message Queue (MQ) Software (3rd)
Redis
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
27
Ranking in other categories
NoSQL Databases (3rd), Managed NoSQL Databases (5th), In-Memory Data Store Services (1st), Vector Databases (3rd), AI Software Development (9th)
 

Featured Reviews

Roberto Costa - PeerSpot reviewer
Senior Data & AI Engineer at Imprint
Facilitates seamless queue creation and management for efficient application decoupling
If you need a messaging service to help decouple your application, Amazon SQS would be a smart choice because it's easy to use and very easy to manage Amazon SQS is a simple service to use. If we compare with other solutions such as RabbitMQ for messaging, Amazon SQS is easier to use and easier…
RituRaj - PeerSpot reviewer
SDE 2 at Virtusa
Caching has improved response times and reduces database load for high-traffic applications
Redis is very reliable, but it could be improved in areas such as monitoring, debugging, and feasibility into memory use. Better built-in tools for observability would help teams manage it more effectively at scale. Managing memory efficiently and troubleshooting issues can sometimes require additional tooling, so these areas can also be improved.One practical challenge I experienced is managing memory efficiently. Since Redis is in-memory, we need to carefully configure eviction policies and monitor usage. Debugging cache-related issues such as stale data or cache invalidation can sometimes be tricky. Additionally, tuning memory usage and eviction policies needs to be planned very carefully.
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
908,344 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
22%
Financial Services Firm
13%
Comms Service Provider
8%
Construction Company
7%
Financial Services Firm
23%
Computer Software Company
9%
Comms Service Provider
6%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise4
Large Enterprise14
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

What needs improvement with Amazon SQS?
There is nothing I can remember that I would want as new features for Amazon SQS.
What is your primary use case for Amazon SQS?
If you need a messaging service to help decouple your application, Amazon SQS would be a smart choice because it's easy to use and very easy to manage.
What advice do you have for others considering Amazon SQS?
I would recommend Amazon SQS to other people. On a scale of 1-10, I rate this solution a 10.
What needs improvement with Redis?
Making management easier, especially for teams operating large Redis clusters, would be helpful. More advanced built-in observability, performance insights, and automated recommendations would help...
What is your primary use case for Redis?
Redis is used primarily as a caching layer to provide a high-performance caching solution that improves application response times and reduces load on backend services and databases. We use it main...
What advice do you have for others considering Redis?
There are a couple of things to consider when using Redis. It is a supporting layer, not a main database. Identifying specific use cases where Redis can provide the most value, such as caching, ses...
 

Comparisons

 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

EMS, NASA, BMW, Capital One
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about Amazon SQS vs. Redis and other solutions. Updated: August 2026.
908,344 professionals have used our research since 2012.