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."
"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."
"I like how we can subscribe to multiple topics in Amazon SQS. It's also much simpler and quicker to set up than other solutions. It also supports patterns like Kafka and RapidMQ's fan-out pattern but with easier implementation."
"The scale it manages is quite impressive."
"The most valuable feature of Amazon SQS is its scalability."
"It works consistently and is economical under a standard non-FIFO model."
"The libraries that connect and manage the queues are rich in features."
"We use the tool in interface integrations."
"What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"Redis is a simple, powerful, and fast solution."
"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 use Redis efficiently."
"I use Redis mostly to cache repeated data that is required."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"The product offers fast access to my database."
 

Cons

"There are some issues with SQS's transaction queue regarding knowing if something has been received."
"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."
"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."
"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."
"The cost became an issue, leading us to consider other solutions."
"There is room for improvement by making use of Kafka services to create more flexible data streams."
"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."
"The solution is not available on-premises so that rules out any customers looking for the messaging solution on-premises."
"If we use a lot of data, it will eventually cost us a lot."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"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."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"The initial setup took some time as our technical team needed to familiarize themselves 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."
"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
 

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."
"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 moderately priced."
"I rate the tool's pricing a nine out of ten."
"SQS's pricing is very good - I would rate it 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."
"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."
"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."
"Redis is an open-source product."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
847,862 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
18%
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 use Redis to manage live chat sys...
 

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.
847,862 professionals have used our research since 2012.