Amazon SQS vs Redis comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Amazon SQS
Average Rating
8.2
Number of Reviews
14
Ranking in other categories
Message Queue (MQ) Software (5th)
Redis
Average Rating
8.4
Number of Reviews
11
Ranking in other categories
Database as a Service (6th), In-Memory Data Store Services (1st), Vector Databases (4th)
 

Market share comparison

As of June 2024, in the Message Queue (MQ) Software category, the market share of Amazon SQS is 11.7% and it increased by 5.0% compared to the previous year. The market share of Redis is 6.4% and it increased by 145.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Queue (MQ) Software
Unique Categories:
No other categories found
Database as a Service
1.4%
In-Memory Data Store Services
7.4%
 

Featured Reviews

Iaan Roux - PeerSpot reviewer
Dec 6, 2022
Very resilient with numerous great features including a 256 kilobyte payload
This is an event-driven solution so messages go through the API gateway onto the queue and are then processed from there. We are customers of Amazon The biggest improvement we've seen from SQS is that our backing system is not under strain anymore and messages don't get lost because the queue is…
Souvik Banerjee - PeerSpot reviewer
Feb 3, 2023
An in-memory, key-value data store for fast access
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. I believe as the Redis ecosystem grows, over time, there will be more adoption, and its community will grow. There will be more resources available for support and questions. In terms of features, they are doing a good job and coming up with many new features, such as Redis Search. They have also introduced a new cloud service. However, I haven't used it much, and I'm not that familiar with the Redis ecosystem, so I don't have input on the features they need to build or improve.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"We used SQS for the Kapolei system to ensure that certain tasks were executed precisely once. The first-in, first-out (FIFO) capability was a great feature for us. Additionally, its redundancy out of the box meant we didn't have to worry about missing messages. It provided peace of mind and automatically instilled trust, relieving us of any concerns."
"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."
"SQS is very stable, and it has lots of features."
"The libraries that connect and manage the queues are rich in features."
"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."
"It's very quick and easy to build or set up Amazon SQS."
"With SQS, we can trigger events in various cloud environments. It offers numerous benefits for us."
"There is no setup just some easy configuration required."
"The in-memory data makes it fast."
"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 is a simple, powerful, and fast solution."
"The ability to fetch and save data quickly is valuable."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"The product offers fast access to my database."
"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."
 

Cons

"The tool needs improvement in user-friendliness and discoverability."
"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."
"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."
"There are some issues with SQS's transaction queue regarding knowing if something has been received."
"Sending or receiving messages takes some time, and it could be quicker."
"Be cautious around pay-as-you-use licensing as costs can become expensive."
"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."
"The solution is not available on-premises so that rules out any customers looking for the messaging solution on-premises."
"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."
"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."
"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 only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"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

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

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
16%
Manufacturing Company
8%
Comms Service Provider
5%
Financial Services Firm
18%
Computer Software Company
15%
Manufacturing Company
8%
Educational Organization
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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?
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 begin...
What is your primary use case for Redis?
Our organization's main use case for Redis is to store and load static content for our multi-client products.
 

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: May 2024.
787,226 professionals have used our research since 2012.