Cloudera Distribution for Hadoop and InfluxDB compete in the enterprise data management and time-series database markets, respectively. Cloudera seems to have an upper hand in enterprise capabilities, while InfluxDB offers ease of use.
Features: Cloudera offers enterprise level features, including robust data security, fast processing with Impala, and comprehensive cluster management tools like Cloudera Manager. InfluxDB provides excellent time-series data handling, seamless integration with Grafana, and powerful metric aggregation capabilities.
Room for Improvement: Cloudera faces challenges with complex setups, licensing, and real-time processing speed, also needing improvements in API integration and Spark documentation. InfluxDB requires better configuration management, high availability, and enhanced query language support, along with improved tool integration and data backup solutions.
Ease of Deployment and Customer Service: Cloudera allows complex but flexible deployment across diverse environments, with mixed support experiences highlighting community reliance. InfluxDB offers efficient on-premises and cloud deployments with generally positive support, though reliance on forums and documentation is noted.
Pricing and ROI: Cloudera Distribution is typically expensive with high licensing and support costs, resulting in suitability for large enterprises needing advanced capabilities. InfluxDB is a more cost-effective open-source option, though scaling incurs additional expenses, aligning with organizations seeking cost-efficiency.
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.
The technical support is quite good and better than IBM.
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 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.
We faced challenges but overcame those challenges successfully.
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.
Integrating with Active Directory, managing security, and configuration are the main concerns.
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.
It can be deployed on-premises, unlike competitors' cloud-only solutions.
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.
This is the only solution that is possible to install on-premise.
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.
| Product | Mindshare (%) |
|---|---|
| InfluxDB | 5.3% |
| Cloudera Distribution for Hadoop | 3.6% |
| Other | 91.1% |
| Company Size | Count |
|---|---|
| Small Business | 16 |
| Midsize Enterprise | 9 |
| Large Enterprise | 31 |
| Company Size | Count |
|---|---|
| Small Business | 8 |
| Midsize Enterprise | 4 |
| Large Enterprise | 8 |
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:
InfluxDB Benefits
There are several benefits to using InfluxDB . Some of the biggest advantages the solution offers include:
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.”
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.
