We performed a comparison between Cloudera Distribution for Hadoop and InfluxDB based on real PeerSpot user reviews.
Find out in this report how the two NoSQL Databases solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It is helpful to gather and process data."
"Provides a viable open-source solution for enterprise implementations and reliable, intelligent data analysis."
"The tool can be deployed using different container technologies, which makes it very scalable."
"Very good end-to-end security features."
"We had a data warehouse before all the data. We can process a lot more data structures."
"Cloudera is a very manageable solution with good support."
"We also really like the Cloudera community. You can have any question and will have your answer within a few hours."
"We're now able to store large volumes of data through Cloudera Distribution for Hadoop. We're able to push large volumes of data to the platform, and that used to be a challenge, especially when storing a terabyte of information. This is the area where Cloudera Distribution for Hadoop improved the organization."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"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 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 most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"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."
"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 solution is very powerful."
"Currently, we are using many other tools such as Spark and Blade Job to improve the performance."
"Cloudera Distribution for Hadoop has a limited feature list and a lot of costs involved."
"The dashboard could be improved."
"The solution does not support multiple languages very well and this means users need to create work-arounds to implement some solutions."
"The tool's ability to be deployed on a cloud model is an area of concern where improvements are required."
"Cloudera's support is extremely bad and cannot be relied on."
"It could be faster and more user-friendly."
"There are multiple bugs when we update."
"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."
"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."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"The solution doesn't have much of a user interface."
"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."
"The solution's UI can be more user-friendly."
"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 error logging capability can be improved because the logs are not very informative."
More Cloudera Distribution for Hadoop Pricing and Cost Advice →
Cloudera Distribution for Hadoop is ranked 5th in NoSQL Databases with 47 reviews while InfluxDB is ranked 3rd in NoSQL Databases with 8 reviews. Cloudera Distribution for Hadoop is rated 8.0, while InfluxDB is rated 7.6. The top reviewer of Cloudera Distribution for Hadoop writes "Good end-to-end security features and we like that it's cloud independent". On the other hand, the top reviewer of InfluxDB writes "A powerful, lightweight time series database with a simple query language and easy setup". Cloudera Distribution for Hadoop is most compared with Amazon EMR, HPE Ezmeral Data Fabric, Apache Spark, MongoDB and Vertica, whereas InfluxDB is most compared with MongoDB, Cassandra, Netdata, ScyllaDB and Couchbase. See our Cloudera Distribution for Hadoop vs. InfluxDB 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.