

InfluxDB and Redis both compete in the time-series data management and caching categories. InfluxDB's rich features and integration capabilities appear to give it an edge in handling complex data scenarios.
Features: InfluxDB offers a robust set of features ideal for handling time-series data, a powerful query language similar to SQL, and integration with Grafana, real-time alerting, and high performance under heavy workloads. Redis is valued for its simplicity, speed, and efficiency as an in-memory data store supporting various data structures, making it a preferred solution for caching and real-time data retrieval.
Room for Improvement: InfluxDB could improve its integration, query language, documentation, high availability, clustering, and support for high-cardinality data. Redis needs better cluster management, enhanced security tools, and greater documentation, with user demands for a GUI and dynamic data handling enhancements.
Ease of Deployment and Customer Service: InfluxDB is available across various cloud and on-premises environments, offering deployment flexibility with generally positive customer service. Redis functions well in cloud and hybrid settings but lacks extensive documentation and relies on community resources for customer support.
Pricing and ROI: InfluxDB offers an open-source solution, with rising costs in cloud environments, delivering ROI through efficiency and reduced downtime. Redis is open-source and cost-effective but may incur higher infrastructure costs due to memory requirements, with ROI found in performance benefits for real-time processing.
These improvements translated into both cost savings and better service reliability, directly impacting business outcomes.
It simplifies processes and reduces the need for additional employees.
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.
It improved API latency from two seconds to 450 milliseconds for P99.
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.
They get on a call, resolve issues, and handle everything efficiently.
The InfluxDB support team was knowledgeable and helped us troubleshoot complex problems efficiently.
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.
The documentation and community support for Redis are very strong, making troubleshooting quicker.
Since Redis is quite stable and well-documented, we have not needed much support, but when required, the response has been helpful.
The main challenge with InfluxDB, which is common with all databases, was handling very high throughput systems and high throughput message flow.
It can handle large volumes of time-series data and with high ingestion rates, making it suitable for enterprise-scale deployments.
We’ve scaled on volume with seven years of continuous data without performance degradation.
Data migration and changes to application-side configurations are challenging due to the lack of automatic migration tools in a non-clustered legacy system.
I scale Redis horizontally using clustering and sharding, where data is distributed across multiple nodes to handle higher traffic and larger data sets.
With features such as clustering and replication, it can handle high traffic and a large database very effectively.
It serves as the backbone of our application, and its stability is crucial.
We have used it to support mission-critical systems with continuous data ingestion and real-time analytics.
It is very stable, with no reliability or downtime in InfluxDB.
Redis is fairly stable.
InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying.
Having a SQL abstraction in InfluxDB could be beneficial, making it more accessible for teams that prefer querying with SQL-style syntax.
It could include automated backup and a monitoring solution for InfluxDB or a script developed by a REST API.
Data persistence and recovery face issues with compatibility across major versions, making upgrades possible but downgrades not active.
Redis itself does not enforce consistency with the primary database, so developers need to carefully design cache invalidation strategies.
One issue is cache invalidation. Keeping cache data consistent with the source of truth can be tricky, especially in distributed systems.
We use the open-source version of InfluxDB, so it is free.
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.
Pricing is based on data volume, retention, and features, which really makes it scalable but requires careful planning to avoid unexpected costs.
Since we use an open-source version of Redis, we do not experience any setup costs or licensing expenses.
The costs are primarily driven by memory consumption and cluster size, since Redis operates in-memory.
The pricing is reasonable for the performance provided.
The most important feature for us is low latency, which is crucial in building a high-performance engine for day trading.
InfluxDB’s core functionality is crucial as it allows us to store our data and execute queries with excellent response times.
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.
It functions similarly to a foundational building block in a larger system, enabling native integration and high functionality in core data processes.
First is its in-memory preference, as Redis is extremely fast, making it ideal for caching and session management where low latency is critical.
Real API latency improved from around two seconds to approximately 450 milliseconds for P99.
| Product | Mindshare (%) |
|---|---|
| Redis | 8.6% |
| InfluxDB | 5.2% |
| Other | 86.2% |


| Company Size | Count |
|---|---|
| Small Business | 9 |
| Midsize Enterprise | 4 |
| Large Enterprise | 8 |
| Company Size | Count |
|---|---|
| Small Business | 11 |
| Midsize Enterprise | 6 |
| Large Enterprise | 10 |
InfluxDB offers efficient time series data handling with fast writes, optimized storage, and seamless Grafana integration, making it ideal for high-volume applications like crypto trading and real-time monitoring. Its SQL-like query language and cloud-based options enhance user experience and system scalability.
InfluxDB stands out with its ability to handle high-volume time series data efficiently, thanks to fast data writes and efficient compression. It is highly scalable, providing clustering features for improved performance management. Integration with Grafana enhances visualization, making it easier to analyze complex data through a user-friendly SQL-like query language. Real-time monitoring, historical data access, and proactive alerts enhance system reliability. Its cloud offering simplifies maintenance and operations, making it attractive for users seeking an efficient time series database.
What are the key features of InfluxDB?InfluxDB is applied extensively in industries handling high-volume data needs. For sensor data storage in production environments, it offers reliable performance. Its role in server management metrics and performance monitoring is crucial for maintaining optimal operations. In crypto market data collection, it supports fast-paced trading environments. Industries use it for real-time tracking, like maritime vessel monitoring, leveraging its rapid data handling and visualization capabilities. Its applications also extend to IoT environments, API performance tracking, HVAC systems, and log aggregation, often integrating with Prometheus, Docker, and AWS to enhance system capabilities.
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?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.
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.