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

"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."
"Amazon SQS is reliable, with no issues to date."
"The most valuable features of the solution are AWS Lambda services, ECS, and QuickSight reports, which are beneficial for data analysis."
"I am able to find out what's going on very easily."
"The most valuable feature of Amazon SQS is the interface."
"The most valuable feature is the ability to decouple components."
"The dead-letter queue is very helpful in maintaining the messages that come into the queue."
"The most valuable features include the ability to handle a huge number of messages and the presence of a dead letter queue."
"The performance of Redis is very fast."
"Redis is good for distributed caching management."
"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."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"The ability to fetch and save data quickly is valuable."
"The solution is fast, provides good performance, and is not too expensive."
"The online interface is very fast and easy to use."
"Redis is a simple service that does what it promises."
 

Cons

"For Amazon SQS, in particular, I think AWS Management Console has shortcomings. AWS Management Console should be a better pluggable option to help users with some integrations."
"Sometimes, we have to switch to another component similar to SQS because the patching tool for SQS is relatively slow for us."
"The solution is not available on-premises so that rules out any customers looking for the messaging solution on-premises."
"The tool needs improvement in user-friendliness and discoverability."
"The search should be more user-friendly, allowing me to search for a longer period of time and return results faster."
"There is room for improvement in the pricing, especially for the FIFO model."
"There are some issues with SQS's transaction queue regarding knowing if something has been received."
"The retention period for messages could be improved. Currently, messages are retained for four or seven days."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"Redis presents a single point of failure and lacks fault tolerance."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"The solution's pricing for a local installation is very expensive."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"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."
 

Pricing and Cost Advice

"Compared to the other options and based on what I have heard, Amazon SQS is relatively more expensive, but it is not insanely expensive."
"I rate the tool's pricing a nine out of ten."
"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."
"Compared to EC2 and other services, Amazon SQS' pricing is cheaper."
"SQS's pricing is very good - I would rate it nine out of ten."
"Amazon SQS is moderately priced."
"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."
"It's quite expensive."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is not an overpriced solution."
"Redis is an open-source solution. There are not any hidden fees."
"Redis is an open-source product."
"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.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
19%
Financial Services Firm
15%
Manufacturing Company
10%
Comms Service Provider
7%
Financial Services Firm
22%
Computer Software Company
14%
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.
851,604 professionals have used our research since 2012.