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
29
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

"It is stable and scalable."
"The most valuable feature is the ability to decouple components."
"There is no setup just some easy configuration required."
"The dead-letter queue is very helpful in maintaining the messages that come into the queue."
"The most valuable feature of Amazon SQS is the interface."
"All Amazon Web Services resources are easy to configure."
"Amazon SQS is reliable, with no issues to date."
"One of the useful features is the ability to schedule a call after a certain number of messages accumulate in the container. For example, if there are ten messages in the container, you can perform a specific action."
"The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"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 acts as an in-memory search tool that improves the speed of operations."
"The solution is fast, provides good performance, and is not too expensive."
"The ability to fetch and save data quickly is valuable."
"The in-memory data makes it fast."
"Redis is a simple service that does what it promises."
 

Cons

"There could be improvements in the UI for security and scalability."
"Be cautious around pay-as-you-use licensing as costs can become expensive."
"There are some issues with SQS's transaction queue regarding knowing if something has been received."
"The search should be more user-friendly, allowing me to search for a longer period of time and return results faster."
"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."
"Sometimes, we have to switch to another component similar to SQS because the patching tool for SQS is relatively slow for us."
"Support could be improved."
"A primary area of improvement for Amazon SQS is the message size limitation, which is currently restricted to 256 kilobytes per message."
"In future releases, I would like Redis to provide its users with an option like schema validation. Currently, the solution lacks to offer such functionality."
"Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"Redis presents a single point of failure and lacks fault tolerance."
"Redis should have an option to operate without Docker on a local PC."
"If we use a lot of data, it will eventually cost us a lot."
"I would prefer it if there was more information available about Redis. That would make it easier for new beginners. Currently, there is a lack of resources."
 

Pricing and Cost Advice

"Amazon SQS is more affordable compared to other solutions."
"Compared to EC2 and other services, Amazon SQS' pricing is cheaper."
"Amazon SQS is moderately priced."
"Compared to the other options and based on what I have heard, Amazon SQS is relatively more expensive, but it is not insanely expensive."
"It's quite expensive."
"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 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."
"Amazon SQS is quite expensive and is at the highest price point compared to other solutions."
"Redis is an open-source product."
"Redis is not an overpriced solution."
"We saw an ROI. It made the processing of our transactions faster."
"The tool is open-source. There are no additional costs."
"Redis is an open-source solution. There are not any hidden fees."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
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?
AWS provides another messaging service, which is fine for certain purposes. SQS meets the cloud messaging workload requirements. However, combining the features of both products could be an easier ...
What is your primary use case for Amazon SQS?
I primarily use SQL Server for messaging services, and I need to offer loose couplings. SQS is handy for offloading non-urgent tasks that can be reverted later. I use it as a queue management servi...
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?
Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation. Additionally, better documentation is neede...
What is your primary use case for Redis?
My primary use case for Redis has been leveraging it as a high-performance, in-memory data store to support real-time features in web applications. For instance, I used Redis to manage live chat sy...
 

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: March 2025.
845,406 professionals have used our research since 2012.