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

InfluxDB 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:
 

ROI

Sentiment score
5.6
InfluxDB enhances efficiency with real-time monitoring automation, reducing manual work and boosting system reliability and uptime.
Sentiment score
7.2
Redis enhances ROI by improving performance, reducing costs, increasing productivity, and ensuring reliable, scalable, and efficient service.
These improvements translated into both cost savings and better service reliability, directly impacting business outcomes.
Senior Data Engineer at a university with 201-500 employees
It simplifies processes and reduces the need for additional employees.
Team Lead, Software at Energybox
InfluxDB reduced my time to show data without any interruption, also reducing the number of people needed to manage the project; it is very good to have InfluxDB in my project.
Student at a educational organization with 1,001-5,000 employees
It improved API latency from two seconds to 450 milliseconds for P99.
Senior Software Developer at NIT
We reduced the database read load by around 30 to 40 percent and improved API response time by 20 to 30 percent, specifically for frequently accessed endpoints.
SDE 2 at Virtusa
 

Customer Service

Sentiment score
5.8
InfluxDB's customer service is efficient with enterprise licenses, yet response times vary; knowledgeable support aids complex issues.
Sentiment score
5.8
Redis is stable and reliable, with helpful support, strong documentation, and often minimal need for direct assistance.
They get on a call, resolve issues, and handle everything efficiently.
DevOps Engineer at Elevenxcapital
The InfluxDB support team was knowledgeable and helped us troubleshoot complex problems efficiently.
Senior Data Engineer at a university with 201-500 employees
Obtaining that quantity of data directly from InfluxDB is quite challenging, and that is why we ask for help from the InfluxDB team to retrieve the data to avoid timeouts and those kinds of issues.
Team Lead, Software at Energybox
The documentation and community support for Redis are very strong, making troubleshooting quicker.
Senior Software Developer at NIT
Since Redis is quite stable and well-documented, we have not needed much support, but when required, the response has been helpful.
SDE 2 at Virtusa
 

Scalability Issues

Sentiment score
7.0
InfluxDB is valued for scalability in handling large data volumes, with enterprise features supporting extensive scale despite variable costs.
Sentiment score
7.8
Redis excels in horizontal and vertical scaling, offering clustering, sharding, and compatibility with Azure and AWS for enterprise adaptability.
The main challenge with InfluxDB, which is common with all databases, was handling very high throughput systems and high throughput message flow.
Deployment Engineer at Derq
It can handle large volumes of time-series data and with high ingestion rates, making it suitable for enterprise-scale deployments.
Senior Data Engineer at a university with 201-500 employees
We’ve scaled on volume with seven years of continuous data without performance degradation.
Senior System Developer at Norled
Data migration and changes to application-side configurations are challenging due to the lack of automatic migration tools in a non-clustered legacy system.
Data Engineer at a photography company with 1,001-5,000 employees
I scale Redis horizontally using clustering and sharding, where data is distributed across multiple nodes to handle higher traffic and larger data sets.
Senior Software Developer at NIT
With features such as clustering and replication, it can handle high traffic and a large database very effectively.
SDE 2 at Virtusa
 

Stability Issues

Sentiment score
8.0
InfluxDB is generally stable, with some crash reports; praised support, but monitoring metrics is recommended for mission-critical use.
Sentiment score
7.8
Redis is stable, handles heavy loads, offers high availability, and uses persistence mechanisms, making it a trusted choice.
It serves as the backbone of our application, and its stability is crucial.
Senior System Developer at Norled
We have used it to support mission-critical systems with continuous data ingestion and real-time analytics.
Senior Data Engineer at a university with 201-500 employees
It is very stable, with no reliability or downtime in InfluxDB.
Student at a educational organization with 1,001-5,000 employees
Redis is fairly stable.
Data Engineer at a photography company with 1,001-5,000 employees
 

Room For Improvement

InfluxDB should enhance its query language, scalability, documentation, and integration while improving performance, security, and pricing flexibility.
Redis users face challenges with scalability, GUI, documentation, security, and seek enhancements in monitoring, analytics, and multi-tenancy features.
InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying.
Chief Technology Officer at Presta Agency
Having a SQL abstraction in InfluxDB could be beneficial, making it more accessible for teams that prefer querying with SQL-style syntax.
Senior System Developer at Norled
It could include automated backup and a monitoring solution for InfluxDB or a script developed by a REST API.
Network engineer at a energy/utilities company with 10,001+ employees
Data persistence and recovery face issues with compatibility across major versions, making upgrades possible but downgrades not active.
Data Engineer at a photography company with 1,001-5,000 employees
Redis itself does not enforce consistency with the primary database, so developers need to carefully design cache invalidation strategies.
Software Engineer at ValueMomentum
One issue is cache invalidation. Keeping cache data consistent with the source of truth can be tricky, especially in distributed systems.
Senior Software Developer at NIT
 

Setup Cost

InfluxDB provides cost-effective scalability for enterprises, but requires careful cost planning due to increasing subscription prices.
Redis pricing depends on memory, cluster size, and infrastructure, with higher costs than SQL due to RAM usage.
We use the open-source version of InfluxDB, so it is free.
Senior System Developer at Norled
I find the cloud version pricing of InfluxDB reasonable, and for the on-premises solution we use in our service, we need to purchase licenses.
Team Lead, Software at Energybox
Pricing is based on data volume, retention, and features, which really makes it scalable but requires careful planning to avoid unexpected costs.
Senior Data Engineer at a university with 201-500 employees
Since we use an open-source version of Redis, we do not experience any setup costs or licensing expenses.
Data Engineer at a photography company with 1,001-5,000 employees
The costs are primarily driven by memory consumption and cluster size, since Redis operates in-memory.
Senior Software Developer at NIT
The pricing is reasonable for the performance provided.
SDE 2 at Virtusa
 

Valuable Features

InfluxDB excels in fast writes, real-time analytics, seamless integration, scalability, and ease of use, enhancing organizational decision-making.
Redis offers low latency, high throughput, and scalability with rich data structures, ideal for real-time applications and caching.
The most important feature for us is low latency, which is crucial in building a high-performance engine for day trading.
Chief Technology Officer at Presta Agency
InfluxDB’s core functionality is crucial as it allows us to store our data and execute queries with excellent response times.
Senior System Developer at Norled
It helps me maintain my solution easily because it is very reliable, so we didn't face any performance issues or crashes regarding our queries; we can get the results very fast.
Solutions Engineer at a tech vendor with 51-200 employees
It functions similarly to a foundational building block in a larger system, enabling native integration and high functionality in core data processes.
Data Engineer at a photography company with 1,001-5,000 employees
First is its in-memory preference, as Redis is extremely fast, making it ideal for caching and session management where low latency is critical.
Software Engineer at ValueMomentum
Real API latency improved from around two seconds to approximately 450 milliseconds for P99.
Senior Software Developer at NIT
 

Categories and Ranking

InfluxDB
Ranking in NoSQL Databases
6th
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
20
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), Network Monitoring Software (13th), IT Infrastructure Monitoring (14th)
Redis
Ranking in NoSQL Databases
4th
Average Rating
8.8
Reviews Sentiment
5.9
Number of Reviews
26
Ranking in other categories
Managed NoSQL Databases (6th), In-Memory Data Store Services (1st), Vector Databases (4th), AI Software Development (13th)
 

Mindshare comparison

As of May 2026, in the NoSQL Databases category, the mindshare of InfluxDB is 5.2%, down from 9.7% compared to the previous year. The mindshare of Redis is 8.6%, up from 6.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis8.6%
InfluxDB5.2%
Other86.2%
NoSQL Databases
 

Featured Reviews

Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.
Varuns Ug - PeerSpot reviewer
Senior Software Developer at NIT
Caching has accelerated complex workflows and delivers low latency for high-traffic microservices
A few features of Redis that I use on a day-to-day basis and feel are among the best are extremely low latency and high throughput. Since Redis is in-memory, it makes it ideal for cases such as caching and rate limiting where response time is critical. TTL expiry support is very useful in Redis as it allows me to automatically evict stale data without manual cleanup, which is something I use heavily in my caching strategy. Another point I can mention is that the rich data structures such as strings, hashes, and even sorted sets are very powerful. I have used strings for caching responses and counters, whereas I have used hashes for storing structured objects. One more feature I can tell you about is atomic operations. Redis guarantees atomicity for operations such as incrementing a counter, which is very useful for rate limiting and avoiding race conditions in distributed systems. Finally, I want to emphasize that Redis is easy to scale and integrate, whether through clustering or using a distributed cache across microservices. Redis has impacted my organization positively by providing default support that is very useful. For metrics, in one of my core systems, introducing Redis as a distributed cache helped me achieve around an 80% cache hit rate, which reduced repeated downstream services. Real API latency also improved from around two seconds to approximately 450 milliseconds for P99. It also helped reduce the load on dependent services and databases, which improved overall system reliability.
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Manufacturing Company
10%
Comms Service Provider
9%
Construction Company
7%
Financial Services Firm
24%
Computer Software Company
10%
Comms Service Provider
7%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise8
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

What needs improvement with InfluxDB?
InfluxDB can be improved by addressing issues such as performance drops, queries being more difficult to understand, and its high memory usage. InfluxDB is not suitable for relational databases lik...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is storing a time series database and analyzing data changes over time. I use InfluxDB to store my infrastructure and application metrics, logs, events, and data, and ...
What advice do you have for others considering InfluxDB?
I would advise others looking into using InfluxDB that if they want to store a time series database for monitoring, logging, and event-based tasks, and also want long-term retention of the database...
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?
Overall, Redis is a powerful and reliable tool, but there are a few areas for improvement. One limitation is that Redis is memory-based, so scaling can become expensive compared to disk-based syste...
What is your primary use case for Redis?
My main use case for Redis is caching frequently accessed data to improve performance and reduce database load. For example, I cache API responses and user-related data so that repeated requests ca...
 

Comparisons

 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
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 InfluxDB vs. Redis and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.