InfluxDB vs Redis comparison

InfluxData and RedisLabs are both solutions in the NoSQL Databases category. InfluxData is ranked #5 with an average rating of 8.7, while RedisLabs is ranked #7 with an average rating of 8.7. InfluxData holds a 6.9% mindshare in ND, compared to RedisLabs’s 8.9% mindshare. Additionally, 100% of InfluxData users are willing to recommend the solution, compared to 100% of RedisLabs users who would recommend it.

InfluxDB

Read 12 InfluxDB reviews

2,961 Views
1,421 Comparison Views

100% willing to recommend

Redis

Read 23 Redis reviews

4,722 Views
756 Comparison Views

100% willing to recommend

InfluxDB

Redis

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Sep 11, 2025

InfluxDB and Redis are competitive in the database realm, each focusing on specific features to excel in distinct use cases. Redis stands out with overall superior performance capabilities, while InfluxDB offers significant strengths in usability and analytics for time-series data.

Features:InfluxDB offers features like high-resolution time-series data handling, efficient data compression, and real-time analytics capabilities, essential for applications requiring detailed data monitoring. Redis is known for fast in-memory data storage, high-speed access, and providing versatile solutions for caching and session storage.

Room for Improvement:InfluxDB could improve in terms of customer support responsiveness, user interface complexity for casual users, and optimizing setup costs for smaller-scale deployments. Redis might enhance support for more complex queries, provide better persistence mechanism options, and offer deeper integration capabilities with external tools for more comprehensive data management.

Ease of Deployment and Customer Service:InfluxDB allows for streamlined cloud deployment with built-in time-series data support, although customer support responsiveness varies. Redis provides robust deployment flexibility with options like managed solutions and on-premise setups, backed by a reputation for highly responsive and efficient customer support.

Pricing and ROI:InfluxDB involves higher initial setup costs, with focus on time-series data capabilities bringing value through detailed analytics. Redis tends to offer lower setup costs, providing quick returns on investment by leveraging its in-memory data store benefits for fast performance. Redis is perceived as yielding quicker ROI due to its speed and efficient performance, making it a cost-effective choice for long-term use.

To learn more, read our detailed InfluxDB vs. Redis Report (Updated: September 2025).

Buyer's Guide

InfluxDB vs. Redis

September 2025

Download the complete report

Helped 868,759 peers since 2012

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

5th

Average Rating

8.2

Reviews Sentiment

6.8

Number of Reviews

Ranking in other categories

Non-Relational Databases (2nd), Open Source Databases (9th), Network Monitoring Software (27th), IT Infrastructure Monitoring (26th)

Redis

Ranking in NoSQL Databases

7th

Average Rating

8.8

Reviews Sentiment

5.7

Number of Reviews

Ranking in other categories

Managed NoSQL Databases (9th), In-Memory Data Store Services (1st), Vector Databases (4th)

Mindshare comparison

As of October 2025, in the NoSQL Databases category, the mindshare of InfluxDB is 6.9%, down from 12.2% compared to the previous year. The mindshare of Redis is 8.9%, up from 1.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.

NoSQL Databases Market Share Distribution
Product	Market Share (%)
InfluxDB	6.9%
Redis	8.9%
Other	84.2%

NoSQL Databases

Featured Reviews

DeepakR

Site Reliability Engineer(Observability) at Sapiens

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.

Read full review

Yaseer Arafat

.Net Developer at Freelance

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.

Read full review

Quotes from Members

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

Pros

"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."

"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."

"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."

"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."

"The solution is very powerful."

"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."

"The most valuable features are aggregating the data and integration with Graphana for monitoring."

More InfluxDB pros

"The ability to fetch and save data quickly is valuable."

"The online interface is very fast and easy to use."

"The solution is fast, provides good performance, and is not too expensive."

"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."

"What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting."

"The in-memory data makes it fast."

"Redis is a simple service that does what it promises."

More Redis pros

Cons

"The error logging capability can be improved because the logs are not very informative."

"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."

"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."

"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."

"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."

"The solution's UI can be more user-friendly."

"I've tried both on-premises and cloud-based deployments, and each has its limitations."

"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."

More InfluxDB cons

"The initial setup took some time as our technical team needed to familiarize themselves with Redis."

"The solution's pricing for a local installation is very expensive."

"For the PubSub feature, we had to create our own tools to monitor the events."

"If we use a lot of data, it will eventually cost us a lot."

"It's actually quite expensive."

"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."

"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."

More Redis cons

Pricing and Cost Advice

"InfluxDB is open-source, but there are additional costs for scaling."

"InfluxDB recently increased its price. It is very expensive now."

"We are using the open-source version of InfluxDB."

"The tool is an open-source product."

"We saw an ROI. It made the processing of our transactions faster."

"The tool is open-source. There are no additional costs."

"Redis is an open-source product."

"Redis is not an overpriced solution."

"Redis is an open-source solution. There are not any hidden fees."

See which vendors are best for you

Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.

See recommendations

868,759 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

11%

Computer Software Company

10%

Manufacturing Company

University

Financial Services Firm

25%

Computer Software Company

12%

Educational Organization

Comms Service Provider

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	4
Midsize Enterprise	3
Large Enterprise	6

By reviewers
Company Size	Count
Small Business	11
Midsize Enterprise	3
Large Enterprise	8

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 ...

See all answers

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...

See all answers

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...

See all answers

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...

See all answers

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...

See all answers

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...

See all answers

Comparisons

ClickHouse vs InfluxDB

Compared 26% of the time

MongoDB Enterprise Advanced vs InfluxDB

Compared 16% of the time

SQLite vs InfluxDB

Compared 7% of the time

PostgreSQL vs InfluxDB

Compared 6% of the time

MySQL vs InfluxDB

Compared 4% of the time

More InfluxDB Competitors

Red Hat Data Grid vs Redis

Compared 10% of the time

Oracle Coherence vs Redis

Compared 10% of the time

Chroma vs Redis

Compared 8% of the time

ScyllaDB vs Redis

Compared 6% of the time

Microsoft Azure Cosmos DB vs Redis

Compared 2% of the time

More Redis Competitors

Product Reports

Buyer's Guide

InfluxDB

September 2025

Download InfluxDB product report

Buyer's Guide

Redis

September 2025

Download Redis product report

Also Known As

No data available

Redis Enterprise

Overview

InfluxDB is open-source software that helps developers and enterprises alike to collect, store, process, and visualize time series data and to build next-generation applications. InfluxDB provides monitoring and insight on IoT, application, system, container, and infrastructure quickly and easily without complexities or compromises in scale, speed, or productivity.

InfluxDB has become a popular insight system for unified metrics and events enabling the most demanding SLAs. InfluxDB is used in just about every type of industry across a wide range of use cases, including network monitoring, IoT monitoring, industrial IoT, and infrastructure and application monitoring.

InfluxDB offers its users:

Infrastructure and application monitoring: Collect, process, and analyze real-time data from edge devices to help optimize distributed infrastructure.

IoT monitoring and analytics: InfluxDB is designed to store large volumes of time series data and quickly perform real-time analysis on that data. Gain insights from all the sensor data and use the collected data to create and perform automated tasks.

Network monitoring: Manage responsive and high-performing networks with widely distributed resources.

InfluxDB Benefits

There are several benefits to using InfluxDB . Some of the biggest advantages the solution offers include:

APIs and ready toolset: InfluxDB can be accessed via a set of powerful tools enabling users to get started quickly, with less programming required. This includes a REST API, extensive client libraries, a wide variety of open-source integrations, and Flux - a functional data scripting language for querying, analysis, and events. The InfluxDB API can be used to write data from edge devices to the InfluxDB instance

Time series engine: Get any data - events, logs, traces - from any edge device - systems, sensors, queues, databases, and networks. This data is stored in a powerful and high-performing engine capable of ingesting millions of data points per second.

Community: InfluxDB has a large community of cloud and open-source developers ready to assist users.

Ready-made templates: Use InfluxDB Templates, a set of tools with a packager and other ready monitoring solutions. These tools allow users to share their monitoring expertise with coworkers and other community members around the world. The Templates gallery offers available templates for some of the most popular tools and applications.

Enhanced UI: InfluxDB’s UI includes an explorer, dashboarding tools, and a script editor. Use it to easily browse the collected metric and event data and apply common transformations. The dashboarding tool comes with a variety of visualization options that help users view insights from the data. The script editor assists users to quickly master Flux with easily accessible examples, auto-completion, and real-time syntax checking.

Reviews from Real Users

InfluxDB stands out among its competitors for a number of reasons. Two major ones are its flexible integration options and its data aggregation feature.

Shalauddin Ahamad S., a software engineer at a tech services company, notes, “The most valuable features are aggregating the data and the integration with Grafana for monitoring.”

InfluxData

Redis offers high-speed, in-memory storage, renowned for real-time performance. It supports quick data retrieval and is used commonly in applications like analytics and gaming.

Renowned for real-time performance, Redis delivers high-speed in-memory storage, making it a favorite for applications needing quick data retrieval. Its diverse data structures and caching capabilities support a broad array of use cases, including analytics and gaming. Redis ensures robust scalability with master-slave replication and clustering, while its publish/subscribe pattern renders it reliable for event-driven applications. The solution integrates smoothly with existing systems, minimizing performance tuning needs. Although documentation on scalability and security could be improved, Redis remains cost-effective and stable, commonly utilized in cloud environments. Enhancing integration with cloud services like AWS and Google Cloud and refining GUI may improve usability.

What are the key features of Redis?

High Speed: In-memory data storage for swift access.
Scalability: Master-slave replication and clustering for growth.
Data Structures: Supports diverse types for varied uses.
Persistence: RDB snapshots and AOF logs ensure durability.
Integration: Seamless integration reduces tuning efforts.

What should users look for in Redis reviews?

Performance: Real-time data retrieval boosts efficiency.
Cost-Effectiveness: Stable, budget-friendly implementation.
Versatility: Suitable for diverse environments and platforms.
Reliability: Ensures data persistence and high availability.

Redis finds application across industries for tasks like caching to improve application performance and speed, minimizing database load. It enables real-time processing for session storage, push notifications, and analytics. As a messaging platform, Redis handles high traffic and supports replication and clustering for cross-platform scalability.

RedisLabs

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

Buyer's Guide

InfluxDB vs. Redis

September 2025

Free Report: InfluxDB vs. Redis

Find out what your peers are saying about InfluxDB vs. Redis and other solutions. Updated: September 2025.

DOWNLOAD NOW

868,759 professionals have used our research since 2012.

See our InfluxDB vs. Redis report.

See our list of best NoSQL Databases vendors.

We monitor all NoSQL Databases reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.