

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.
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.
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.
We have seen a positive return on investment from using Redis, mainly through improved application performance, reduced database load, and lower operational overhead.
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.
By simply referring to their documentation, we have been able to fix our bugs and general issues.
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.
The in-memory architecture provides consistently low-latency access even as data access patterns and request volume increase.
Data migration and changes to application-side configurations are challenging due to the lack of automatic migration tools in a non-clustered legacy system.
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 has consistently provided fast and predictable performance, particularly for caching and high-frequency data access scenarios.
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.
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.
Data persistence and recovery face issues with compatibility across major versions, making upgrades possible but downgrades not active.
Redis is very reliable, but it could be improved in areas such as monitoring, debugging, and feasibility into memory use.
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.
The main value comes from the performance improvements, reduced database load, and increased scalability that Redis provides.
Since we use an open-source version of Redis, we do not experience any setup costs or licensing expenses.
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.
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.
The most valuable features include high-speed in-memory data access, flexible data structures, caching capabilities, data expiration and time-to-live management, high availability and scalability, and atomic operations.
| Product | Mindshare (%) |
|---|---|
| Redis | 7.8% |
| InfluxDB | 5.1% |
| Other | 87.1% |


| Company Size | Count |
|---|---|
| Small Business | 9 |
| Midsize Enterprise | 5 |
| Large Enterprise | 9 |
| Company Size | Count |
|---|---|
| Small Business | 13 |
| 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 is an advanced in-memory data store renowned for its high-speed data access, flexibility, and key expiration capabilities, supporting numerous data structures for seamless scalability and performance.
Redis provides exceptional in-memory data management with diverse data structures like strings, hashes, and sorted sets. It ensures high performance, minimal latency, and seamless integration with existing systems to boost scalability and efficiency. Commonly used for caching, session management, and rate limiting, Redis significantly reduces database load and enhances application responsiveness while offering room for improvement in areas like documentation and monitoring tools. Users seek better scalability, security features, and persistency for extensive datasets.
What are the key features of Redis?Redis solutions are prominently deployed in industries requiring rapid data retrieval such as real-time financial services, e-commerce platforms, and social media applications. They support low-latency access and are crucial for managing high-traffic user sessions and API responses, ensuring robust performance and reliability across diverse application environments.
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.