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 (5th)
 

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 the tool in interface integrations."
"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."
"It works consistently and is economical under a standard non-FIFO model."
"All Amazon Web Services resources are easy to configure."
"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 libraries that connect and manage the queues are rich in features."
"Amazon SQS is reliable, with no issues to date."
"The most valuable feature of Amazon SQS is its scalability."
"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."
"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."
"The ability to fetch and save data quickly is valuable."
"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."
"Redis is good for distributed caching management."
"I use Redis mostly to cache repeated data that is required."
"Redis acts as an in-memory search tool that improves the speed of operations."
 

Cons

"There is room for improvement in handling large-scale data."
"The tool needs improvement in user-friendliness and discoverability."
"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."
"There is room for improvement by making use of Kafka services to create more flexible data streams."
"Packages sometimes have delays in dropping, indicating reliability issues."
"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."
"I cannot send a message to multiple people simultaneously. It can only be sent to one recipient."
"There is room for improvement in the pricing, especially for the FIFO model."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"If we use a lot of data, it will eventually cost us a lot."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"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."
"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."
"Redis presents a single point of failure and lacks fault tolerance."
"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."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
 

Pricing and Cost Advice

"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."
"Amazon SQS is more affordable compared to other solutions."
"SQS's pricing is very good - I would rate it nine out of ten."
"Amazon SQS is moderately priced."
"It's quite expensive."
"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 quite expensive and is at the highest price point compared to other solutions."
"Redis is not an overpriced solution."
"The tool is open-source. There are no additional costs."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source product."
"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.
838,640 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
16%
Manufacturing Company
10%
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?
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.
838,640 professionals have used our research since 2012.