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

"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."
"There is no setup just some easy configuration required."
"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 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."
"All Amazon Web Services resources are easy to configure."
"The libraries that connect and manage the queues are rich in features."
"Amazon SQS provides faster search through indexing via OpenSearch."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"It is particularly efficient for cloud-based storage and operations."
"The online interface is very fast and easy to use."
"The product offers fast access to my database."
"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 solution is fast, provides good performance, and is not too expensive."
"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 a simple service that does what it promises."
 

Cons

"A primary area of improvement for Amazon SQS is the message size limitation, which is currently restricted to 256 kilobytes per message."
"Sometimes, we have to switch to another component similar to SQS because the patching tool for SQS is relatively slow for us."
"It would be beneficial to have the ability to peek at messages currently in Amazon SQS without needing to monitor incoming messages."
"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."
"I cannot send a message to multiple people simultaneously. It can only be sent to one recipient."
"There is room for improvement by making use of Kafka services to create more flexible data streams."
"Be cautious around pay-as-you-use licensing as costs can become expensive."
"There is room for improvement in handling large-scale data."
"If we use a lot of data, it will eventually cost us a lot."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"Redis presents a single point of failure and lacks fault tolerance."
"For the PubSub feature, we had to create our own tools to monitor the events."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"It's actually quite expensive."
"The solution's pricing for a local installation is very expensive."
"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

"SQS's pricing is very good - I would rate it nine out of ten."
"Amazon SQS is moderately priced."
"Amazon SQS is more affordable compared to other solutions."
"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 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."
"Compared to EC2 and other services, Amazon SQS' pricing is cheaper."
"The pricing model is pay-as-you-use. It depends on your usage and configuration."
"Redis is not an overpriced solution."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source product."
"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.
842,296 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Computer Software Company
17%
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: March 2025.
842,296 professionals have used our research since 2012.