We performed a comparison between Cloudera Distribution for Hadoop, InfluxDB, and Neo4j Graph Database based on real PeerSpot user reviews.
Find out what your peers are saying about MongoDB, Couchbase, InfluxData and others in NoSQL Databases."The file system is a valuable feature."
"The most valuable feature is that I can use CDH for almost all use cases across all industries, including the financial sector, public sector, private retailers, and so on."
"The most valuable feature is Impala, the querying engine, which is very fast."
"The main advantage is the storage is less expensive."
"The product provides better data processing features than other tools."
"The tool can be deployed using different container technologies, which makes it very scalable."
"It has the best proxy, security, and support features compared to open-source products."
"CDH has a wide variety of proprietary tools that we use, like Impala. So from that perspective, it's quite useful as opposed to something open-source. We get a lot of value from Cloudera's proprietary tools."
"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 features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"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 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."
"The solution is very powerful."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"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."
"Creates the ability to visualize outputs."
"As a graph database, I am surprised at their performance and response time."
"Enables people to understand what the business problem is and how the technology helps."
"The security of this solution could be improved. There should also be a way to basically have a blockchain enabled storage with the HDFS."
"While the deployed product is generally functional, there are instances where it presents difficulties."
"There are multiple bugs when we update."
"The initial setup of Cloudera is difficult."
"Cloudera Distribution for Hadoop is not always completely stable in some cases, which can be a concern for big data solutions."
"There are better solutions out there that have more features than this one."
"It would be useful if Cloudera had more tools like SQL Engines that offer the traditional relational database. We have to do a lot of work preparing the data outside Cloudera before getting it into the platform."
"The solution does not support multiple languages very well and this means users need to create work-arounds to implement some solutions."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"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."
"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 solution's UI can be more user-friendly."
"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."
"The solution doesn't have much of a user interface."
"The error logging capability can be improved because the logs are not very informative."
"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."
"So far, we have not had any issues and are happy with the product in general."
"There are concerns about performance and whether the tool can necessarily scale to provide the solution."
More Cloudera Distribution for Hadoop Pricing and Cost Advice →