Try our new research platform with insights from 80,000+ expert users

InfluxDB vs Redis comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 2025

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

InfluxDB
Ranking in NoSQL Databases
3rd
Average Rating
8.2
Reviews Sentiment
6.6
Number of Reviews
11
Ranking in other categories
Non-Relational Databases (2nd), Open Source Databases (9th), Network Monitoring Software (23rd), IT Infrastructure Monitoring (24th)
Redis
Ranking in NoSQL Databases
7th
Average Rating
8.8
Reviews Sentiment
5.7
Number of Reviews
23
Ranking in other categories
In-Memory Data Store Services (1st), Vector Databases (4th)
 

Mindshare comparison

As of August 2025, in the NoSQL Databases category, the mindshare of InfluxDB is 7.6%, down from 12.4% compared to the previous year. The mindshare of Redis is 9.2%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases
 

Featured Reviews

DeepakR - PeerSpot reviewer
An open-source database that can be used to insert data
InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times.
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

"The user interface is well-designed and easy to use. It provides a clear overview of the data, making it simple to understand the information at hand."
"InfluxDB's best feature is that it's a cloud offering. Other good features include its time-series DB, fast time-bulk queries, and window operations."
"InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data from servers. It must be installed on Windows or Linux servers. During installation, ensure that the configuration file is correct to prevent issues. Once data is collected, it can be sent to InfluxDB. For visualization, you can use open-source tools like Grafana."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"The solution is very powerful."
"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 is a simple, powerful, and fast solution."
"The in-memory data makes it fast."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"I use Redis mostly to cache repeated data that is required."
"Redis is a simple service that does what it promises."
"Redis acts as an in-memory search tool that improves the speed of operations."
"The solution is fast, provides good performance, and is not too expensive."
 

Cons

"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"The solution doesn't have much of a user interface."
"The error logging capability can be improved because the logs are not very informative."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"The solution's UI can be more user-friendly."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"It's actually quite expensive."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
"Redis should have an option to operate without Docker on a local PC."
"If we use a lot of data, it will eventually cost us a lot."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"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 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."
 

Pricing and Cost Advice

"The tool is an open-source product."
"We are using the open-source version of InfluxDB."
"InfluxDB recently increased its price. It is very expensive now."
"InfluxDB is open-source, but there are additional costs for scaling."
"Redis is not an overpriced solution."
"Redis is an open-source product."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source solution. There are not any hidden fees."
"The tool is open-source. There are no additional costs."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
864,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
12%
Manufacturing Company
9%
Comms Service Provider
8%
Financial Services Firm
24%
Computer Software Company
13%
Educational Organization
7%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about InfluxDB?
InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data ...
What needs improvement with InfluxDB?
It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster. Replicating data for on-prem development and testing is difficult. Having a SQL abstrac...
What is your primary use case for InfluxDB?
InfluxDB is the main component in our large enterprise-scale streaming data application for maritime vessels. We collect position data from vessels around the coast once per second, put it on a Kaf...
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 disadvantage of Redis is that it's a little bit hard to have too many clusters or too many nodes and create the clusters. The sync between the nodes is easier to implement with Couchbase, for e...
What is your primary use case for Redis?
Redis is used for a part of a booking engine for travel, specifically for the front part to get some sessions and information about the sessions. If a customer or user is using the sites in differe...
 

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: July 2025.
864,053 professionals have used our research since 2012.