No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon Timestream vs Redis comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 2026

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 Timestream
Ranking in Managed NoSQL Databases
7th
Average Rating
9.0
Reviews Sentiment
6.9
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Redis
Ranking in Managed NoSQL Databases
5th
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
26
Ranking in other categories
NoSQL Databases (3rd), In-Memory Data Store Services (1st), Vector Databases (3rd), AI Software Development (9th)
 

Mindshare comparison

As of August 2026, in the Managed NoSQL Databases category, the mindshare of Amazon Timestream is 4.8%, down from 6.9% compared to the previous year. The mindshare of Redis is 7.3%, up from 2.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis7.3%
Amazon Timestream4.8%
Other87.9%
Managed NoSQL Databases
 

Featured Reviews

Sushil Pandey - PeerSpot reviewer
Data Engineer at Tiger Analytics
It is helpful to get telemetry data from the devices in real-time
It is an easily scalable solution. When it comes to the retention period, if someone wants to change, they have to define it at the start. Later on, if users want to change it again, like, or increase the retention policy, then they have to create the table again and do so, and if it is not done, then we face problems. It will increase the retention, but when you try to insert a record or an older record that is not included in the range of your retention period, then you can face some problems and, like, it will throw some errors. The tool is scalable, but it should be defined at the start as to how much retention you want. For scalability, I rate the tool a six or seven out of ten.
RituRaj - PeerSpot reviewer
SDE 2 at Virtusa
Caching has improved response times and reduces database load for high-traffic applications
Redis is very reliable, but it could be improved in areas such as monitoring, debugging, and feasibility into memory use. Better built-in tools for observability would help teams manage it more effectively at scale. Managing memory efficiently and troubleshooting issues can sometimes require additional tooling, so these areas can also be improved.One practical challenge I experienced is managing memory efficiently. Since Redis is in-memory, we need to carefully configure eviction policies and monitor usage. Debugging cache-related issues such as stale data or cache invalidation can sometimes be tricky. Additionally, tuning memory usage and eviction policies needs to be planned very carefully.

Quotes from Members

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

Pros

"Using Amazon Timestream has been seamless due to its integration within the AWS ecosystem and ease of use for the engineering team."
"The best things about Amazon Timestream are it's maintenance-free, customizable, and has no lag issues. It's always real-time."
"If you drop a message, the solution's technical support will definitely reply."
"What I like best is that the tool is easy to collect and store data and is fast and scalable. The fully managed database is easy to understand."
"You can quickly aggregate data from the last ten years with Amazon Timestream."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"Since I started using Redis, I feel that the product is saving me some performance tuning time."
"I use Redis mostly to cache repeated data that is required."
"The online interface is very fast and easy to use."
"Redis is a powerful and reliable tool for improving application performance."
"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."
"Redis has had a positive impact by improving application performance, reducing database load, and making the system more scalable."
"Redis is a simple service that does what it promises."
 

Cons

"The tool could be improved by increasing the batch size from one hundred records to five hundred or a thousand to speed up indexing."
"Arranging the database schema is a bit challenging."
"The solution could be improved by making it easier for new graduates like me to use. Better explanations of queries and how to use them with other AWS services would help."
"There are certain features that we would like to see added and we are collaborating with the product teams on these areas."
"There are disadvantages when it comes to time series databases since you can't delete anything from Amazon Timestream data."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"There is a lack of documentation on the scalability of the solution."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
"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."
"Making management easier, especially for teams operating large Redis clusters, would be helpful."
"Redis presents a single point of failure and lacks fault tolerance."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"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

"Amazon Timestream's pricing seems manageable to me."
"We don't see high costs with Amazon Timestream, which may vary by company."
"We pay over $10 million a year to Amazon."
"For 1GB of data, the solution charges $ 0.01 in the US region."
"Redis is an open-source product."
"The tool is open-source. There are no additional costs."
"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 Managed NoSQL Databases solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
12%
Computer Software Company
12%
Educational Organization
9%
Financial Services Firm
22%
Computer Software Company
9%
Comms Service Provider
6%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

What needs improvement with Amazon Timestream?
We are working on a few open change requests with the engineering teams on AWS's side. There are certain features that we would like to see added and we are collaborating with the product teams on ...
What is your primary use case for Amazon Timestream?
We use Amazon Timestream as a data historian for IT data. It stores all individual measurements of our customers' IoT devices for a certain period of time, allowing them to perform time-series-base...
What needs improvement with Redis?
Making management easier, especially for teams operating large Redis clusters, would be helpful. More advanced built-in observability, performance insights, and automated recommendations would help...
What is your primary use case for Redis?
Redis is used primarily as a caching layer to provide a high-performance caching solution that improves application response times and reduces load on backend services and databases. We use it main...
What advice do you have for others considering Redis?
There are a couple of things to consider when using Redis. It is a supporting layer, not a main database. Identifying specific use cases where Redis can provide the most value, such as caching, ses...
 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
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 Timestream vs. Redis and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.