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

InfluxDB vs Redis comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

InfluxDB
Ranking in NoSQL Databases
6th
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
9
Ranking in other categories
Non-Relational Databases (5th), Open Source Databases (11th), Network Monitoring Software (61st), IT Infrastructure Monitoring (49th)
Redis
Ranking in NoSQL Databases
7th
Average Rating
8.8
Number of Reviews
21
Ranking in other categories
In-Memory Data Store Services (1st), Vector Databases (4th)
 

Featured Reviews

PedroCampos - PeerSpot reviewer
A powerful, lightweight time series database with a simple query language and easy setup
Influx has TICK Stack, which contains multiple services and multiple products that work together. InfluxDB is just a time series database, and it works really well. I haven't yet had the time to look into the new stack based on Influx 2.0, but currently, as a time series database, InfluxDB is working the way it is supposed to work. In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version. I would also like to have high availability features, such as replication, active-active, etc. If they can put an extra plugin or service on top of it, it would be something interesting. I am not sure if they have high availability to make it data center-aware for clustering. For example, I am not sure whether you can have it at different locations with big clusters that are location-aware. Even in their documentation or presentation, they talk too little about high availability and extended clusters with different locations. They might already have it in the newer versions. We have Influx 1.8 in our production in the stage and internal workloads environments. The other products in their ecosystem, such as Chronograf, can be improved. Chronograf is a dashboarding or visualization layer product, and that, for sure, can be improved.
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 most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"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 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."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"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."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"In our case, it started with a necessity to fill the gap that we had in monitoring. We had very reactive monitoring without trend analysis and without some advanced features. We were able to implement them by using a time series database. We are able to have all the data from applications, logs, and systems, and we can use a simple query language to correlate all the data and make things happen, especially with monitoring. We could more proactively monitor our systems and our players' trends."
"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"The product offers fast access to my database."
"The in-memory data makes it fast."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"Redis is a simple, powerful, and fast solution."
"It is particularly efficient for cloud-based storage and operations."
"Redis is good for distributed caching management."
"I use Redis mostly to cache repeated data that is required."
 

Cons

"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"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."
"The solution doesn't have much of a user interface."
"The solution's UI can be more user-friendly."
"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."
"The error logging capability can be improved because the logs are not very informative."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"The solution's pricing for a local installation is very expensive."
"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."
"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."
"For the PubSub feature, we had to create our own tools to monitor the events."
"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."
"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 initial setup took some time as our technical team needed to familiarize themselves with Redis."
 

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."
"The tool is open-source. There are no additional costs."
"Redis is an open-source product."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is not an overpriced solution."
"Redis is an open-source solution. There are not any hidden fees."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
825,609 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
12%
Manufacturing Company
9%
Educational Organization
8%
Financial Services Firm
21%
Computer Software Company
15%
Educational Organization
7%
Manufacturing Company
7%
 

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?
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 coll...
What is your primary use case for InfluxDB?
I use the solution to store and manage data from various sensors in a production environment. I have developed a system where data from these sensors is communicated through an OPC UA receiver and ...
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?
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 a...
What is your primary use case for Redis?
My primary use case for Redis is to enhance the performance of our web applications by using it as a caching layer. By caching frequently accessed data, we reduce the load on our primary databases,...
 

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: December 2024.
825,609 professionals have used our research since 2012.