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.1
Number of Reviews
21
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

"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 solution is easy to scale and cost-effective."
"I think the tool is very reliable."
"I am able to find out what's going on very easily."
"With SQS, we can trigger events in various cloud environments. It offers numerous benefits for us."
"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."
"The most valuable features include the ability to handle a huge number of messages and the presence of a dead letter queue."
"The dead-letter queue is very helpful in maintaining the messages that come into the queue."
"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."
"Redis is good for distributed caching management."
"The solution is fast, provides good performance, and is not too expensive."
"The product offers fast access to my database."
"Redis is a simple, powerful, and fast solution."
"The ability to fetch and save data quickly is valuable."
"Redis is a simple service that does what it promises."
 

Cons

"Sometimes, we have to switch to another component similar to SQS because the patching tool for SQS is relatively slow for us."
"Packages sometimes have delays in dropping, indicating reliability issues."
"The search should be more user-friendly, allowing me to search for a longer period of time and return results faster."
"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."
"A primary area of improvement for Amazon SQS is the message size limitation, which is currently restricted to 256 kilobytes per message."
"The cost became an issue, leading us to consider other solutions."
"Amazon SQS is costly. I think there could be improvements in how it facilitates comparisons between different AWS products. A calculator would be helpful. The calculator for Kafka is based on factors like throughput or storage used in the last month. In contrast, the calculator for Amazon SQS is based on the number of transactions processed. These different approaches make it challenging to compare them directly. I suggest AWS provide a straightforward calculator where I can input one aspect, and it calculates costs for multiple solutions."
"There could be improvements in the UI for security and scalability."
"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."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"There is a lack of documentation on the scalability of the solution."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"For the PubSub feature, we had to create our own tools to monitor the events."
"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."
"The solution's pricing for a local installation is very expensive."
 

Pricing and Cost Advice

"Amazon SQS is quite expensive and is at the highest price point compared to other solutions."
"SQS's pricing is very good - I would rate it nine out of ten."
"Amazon SQS is more affordable compared to other solutions."
"It's quite expensive."
"The pricing model is pay-as-you-use. It depends on your usage and configuration."
"Compared to EC2 and other services, Amazon SQS' pricing is cheaper."
"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."
"Redis is not an overpriced solution."
"Redis is an open-source solution. There are not any hidden fees."
"The tool is open-source. There are no additional costs."
"Redis is an open-source product."
"We saw an ROI. It made the processing of our transactions faster."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
831,020 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
15%
Manufacturing Company
10%
Comms Service Provider
6%
Financial Services Firm
21%
Computer Software Company
16%
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?
A primary area of improvement for Amazon SQS is the message size limitation, which is currently restricted to 256 kilobytes per message. If this could be increased, it would benefit many use cases....
What is your primary use case for Amazon SQS?
I have been heavily using Amazon SQS for the last more than four years in serverless and decoupled solutions. We use it in workflows like order creation, where the order creation task is queued, al...
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?
I use Redis as a tool in building projects, specifically for in-memory caching. My backend API uses Redis to cache information retrieved from the database.
 

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: January 2025.
831,020 professionals have used our research since 2012.