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.8
Companies experienced enhanced operational efficiency and increased customer satisfaction with InfluxDB through real-time monitoring and automation.
Sentiment score
7.3
Redis boosts performance and reduces costs, enhancing API latency and productivity while allowing focus on feature development.
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
It has reduced a lot of time in terms of troubleshooting because the way it produces the data on a time-series basis allows me to collect and store the data for future reference.
Sdet Performance Engineer at a tech vendor with 10,001+ employees
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
We have seen a positive return on investment from using Redis, mainly through improved application performance, reduced database load, and lower operational overhead.
Senior Software Engineer at a consultancy with 1-10 employees
 

Customer Service

Sentiment score
5.8
InfluxDB customer support is praised for enterprise-level help but needs faster response times and more complex deployment support.
Sentiment score
6.4
Redis users rarely need support due to stability, relying on documentation and community, with mixed experiences reported.
They get on a call, resolve issues, and handle everything efficiently.
Senior Dev Ops Engineer at 11 East Capital
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
By simply referring to their documentation, we have been able to fix our bugs and general issues.
Senior Software Engineer at a consultancy with 1-10 employees
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 scales efficiently in enterprises, supports large data volumes, and integrates well, though backup stability varies by deployment.
Sentiment score
7.8
Redis excels in scalability and efficiency, handling high traffic with clustering and sharding, benefiting enterprise application demands.
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
The in-memory architecture provides consistently low-latency access even as data access patterns and request volume increase.
Senior Software Engineer at a consultancy with 1-10 employees
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
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 reliable, stable, and supported, with minor issues resolved by integrations and support, except in Azure China.
Sentiment score
7.9
Redis is lauded for its stability, reliable caching performance, and robust architecture, supported by strong community and managed services.
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 has consistently provided fast and predictable performance, particularly for caching and high-frequency data access scenarios.
Senior Software Engineer at a consultancy with 1-10 employees
Redis is fairly stable.
Data Engineer at a photography company with 1,001-5,000 employees
 

Room For Improvement

InfluxDB requires improvements in query language, UI, pricing, documentation, scalability, cloud integration, and support for non-technical users.
Redis users seek improvements in cache management, user interface, observability, scalability, security setup, and cloud integrations for enhanced usability.
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
Making security features and enterprise governance capabilities easier to configure out of the box would help organizations adopt Redis more confidently for larger and more critical workloads.
Senior Software Engineer at a consultancy with 1-10 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
 

Setup Cost

InfluxDB's pricing shift to a monthly model prompts enterprises to consider open-source options for cost-effective scalability and flexibility.
Enterprise Redis costs vary by deployment model, with self-managed being cost-effective and cloud services charging for memory 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
The main value comes from the performance improvements, reduced database load, and increased scalability that Redis provides.
Senior Software Engineer at a consultancy with 1-10 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 pricing is reasonable for the performance provided.
SDE 2 at Virtusa
 

Valuable Features

InfluxDB excels in fast data writes, analytics, and integration, enhancing efficiency and visualization with robust community support.
Redis is preferred for speed and reliability, offering low latency, high throughput, and efficient scaling with minimal configuration.
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
By offloading frequent reads from the database and enabling fast in-memory cache access, it reduced latency, improved throughput, and helped maintain stability during peak loads.
SDE 2 at Virtusa
 

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 (6th), Network Monitoring Software (14th), IT Infrastructure Monitoring (12th)
Redis
Ranking in NoSQL Databases
3rd
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
27
Ranking in other categories
Managed NoSQL Databases (5th), In-Memory Data Store Services (1st), Vector Databases (3rd), AI Software Development (9th)
 

Mindshare comparison

As of August 2026, in the NoSQL Databases category, the mindshare of InfluxDB is 5.2%, down from 7.6% compared to the previous year. The mindshare of Redis is 8.3%, down from 9.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis8.3%
InfluxDB5.2%
Other86.5%
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.
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.
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise5
Large Enterprise9
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

What needs improvement with InfluxDB?
If the dashboarding facility can be improved in terms of the visualization parameters and the amount of support available from the community, as well as having smarter alerts to send those alerts t...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is to inject all my performance data and visualize it as a data source into Grafana. My data comes from JMeter from a plugin, which is inserting data to InfluxDB, and ...
What advice do you have for others considering InfluxDB?
It is good to start with InfluxDB to stabilize your data, visualize your data, and have the data stored on a time-series basis. I would recommend everyone to get into InfluxDB and start using it. T...
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...
 

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: June 2026.
908,800 professionals have used our research since 2012.