Try our new research platform with insights from 80,000+ expert users

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:
 

Categories and Ranking

Amazon SQS
Average Rating
8.6
Reviews Sentiment
7.4
Number of Reviews
30
Ranking in other categories
Message Queue (MQ) Software (3rd)
Redis
Average Rating
8.8
Reviews Sentiment
8.0
Number of Reviews
22
Ranking in other categories
NoSQL Databases (7th), In-Memory Data Store Services (1st), Vector Databases (4th)
 

Featured Reviews

Ariel Tarayants - PeerSpot reviewer
Powerful queue system facilitates seamless asynchronous operations
A feature I would like to see in Amazon SQS is the ability to view the content of messages without removing them from the queue. Enhanced filtering on the messages would be beneficial, as currently one has to pull all messages out, filter the right one by code, and then re-insert the remaining messages. This solution is not effective with the FIFO queue.
Yaseer Arafat - PeerSpot reviewer
Unmatched Performance and Scalability for Modern Applications
Redis has room for improvement in a few areas. Enhanced tools for managing and monitoring clusters would be beneficial, as would built-in security mechanisms like advanced encryption and granular access controls. Simplifying setup and configuration could make Redis more accessible to new users. Introducing more enterprise-grade features, such as better multi-tenancy support and improved backup and restore capabilities, would also be advantageous. For the next release, it would be great to see enhanced cluster management tools, native multi-region supports for better data redundancy, integrated analytics for deeper insights, AI and ML integration features, and improved developer experience through enhanced SDKs and tools.

Quotes from Members

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

Pros

"The most valuable feature is the ability to decouple components."
"The libraries that connect and manage the queues are rich in features."
"The most valuable feature of Amazon SQS is its scalability."
"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."
"The scale it manages is quite impressive."
"With SQS, we can trigger events in various cloud environments. It offers numerous benefits for us."
"It's very quick and easy to build or set up Amazon SQS."
"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."
"I use Redis mostly to cache repeated data that is required."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"The product offers fast access to my database."
"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."
"The online interface is very fast and easy to use."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
 

Cons

"Support could be improved."
"Be cautious around pay-as-you-use licensing as costs can become expensive."
"It would be easier to have a dashboard that allows us to see everything and manage everything since we have so many queues."
"The search should be more user-friendly, allowing me to search for a longer period of time and return results faster."
"There could be improvements in the UI for security and scalability."
"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."
"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."
"The tool needs improvement in user-friendliness and discoverability."
"Redis should have an option to operate without Docker on a local PC."
"It's actually quite expensive."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
"There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"There is a lack of documentation on the scalability of the solution."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
 

Pricing and Cost Advice

"SQS's pricing is very good - I would rate it nine out of ten."
"Amazon SQS offers a generous free tier, beyond which it remains very cost-effective. The cost per million messages is less than a dollar, making it an economical choice."
"Compared to the other options and based on what I have heard, Amazon SQS is relatively more expensive, but it is not insanely expensive."
"Amazon SQS is moderately priced."
"I rate the tool's pricing a nine out of ten."
"The pricing model is pay-as-you-use. It depends on your usage and configuration."
"Amazon SQS is more affordable compared to other solutions."
"Amazon SQS is quite expensive and is at the highest price point compared to other solutions."
"Redis is an open-source product."
"Redis is an open-source solution. There are not any hidden fees."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is not an overpriced solution."
"The tool is open-source. There are no additional costs."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
849,686 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
16%
Manufacturing Company
11%
Comms Service Provider
7%
Financial Services Firm
22%
Computer Software Company
15%
Educational Organization
7%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with Amazon SQS?
The retention period for messages could be improved. Currently, messages are retained for four or seven days. It would be beneficial if there was a provision to configure and retain messages for lo...
What is your primary use case for Amazon SQS?
I primarily use Amazon SQS ( /products/amazon-sqs-reviews ) for asynchronous messaging. It is part of our distributed system design, where we use it for asynchronous communication by posting a mess...
What do you like most about Redis?
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you u...
What needs improvement with Redis?
There are a few areas where Redis could improve. The pub-sub capabilities could be optimized to handle network sessions better, as there are challenges with maintaining sessions between clients and...
What is your primary use case for Redis?
We use Redis ( /products/redis-reviews ) for several purposes, including ranking, counting, saving, sharing, caching, and setting time-to-live notifications. These functionalities are employed acro...
 

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: April 2025.
849,686 professionals have used our research since 2012.