Cloudera Data Platform Reviews

Its ability to scale out seamlessly with little to no effort is very valuable to us. All the tools in the stack are built from the ground up to support massive amounts of data.

It allows us to provide our customers with data insights that they previously were unable to obtain.

There have been some governance initiatives, but they are far from production ready. I would like to see a big improvement in that space, as governance is critical in many regulated industries.

I've been using it for one year.

Stability is good if configured properly, but for some tools such as for instance HBase, configuration is extremely hard to get right.

Scalability is superb.

I never interacted with customer support.

Cloudera and vanilla Big Data tech. We continue to use them alongside HortonWorks, depending on our clients preferences and needs.

Cloudera and vanilla Big Data tech. We continue to use them alongside Hortonworks, depending on our clients preferences and needs.

With Ambari, it is pretty straightforward, but I have no idea why they prefer FQDN over IP.

My colleagues and I are the implementation team. The general advice is to start out with a small enough scope. Try to get an MVP up and running before bringing out the big guns./

Licensing is on a per node basis and it encourages people to scale vertically rather than horizontally yet the whole purpose of the tools they sell is to scale horizontally. I do like that everything is also available freely for those that do not require support.

Make sure you understand what happens under the hood. Out-of-the-box tools are sub-par. Customisation is the way to go for now.

The HDFS (Java-based file system) and Hive Utilities are proving to be most useful.

Hortonworks has allowed my organization to increase the amount of data that we regularly store from sensor data and weblogs, which in turn gives us a greater scope of data to analyze.

I would like to see an increase in usability for the Apache Storm engine within the data platform.

I have been using it for less than a year.

When initializing our cluster, we did not allocate enough space to our VAR partition and that ended up causing some issues with the networking to our onsite Tomcat server.

It's fairly low customer service.

It's fairly low technical support.

We started off with this product.

Both straightforward and complex, everything was easy to set up, but a lot of the behind the scenes configuration changes for customization could be rather time consuming.

We used an in-house team. My advice is to study hard and read all the documentation thoroughly before starting any implementation. It is paramount that one understands the system before implementing it.

Current ROI is none as we are still in the POC phase with most of our products.

Be sure that the product is necessary for the situation.

There’s not only one, the all-stack of Hadoop is valuable, the distributed file system HDFS, Spark, Kafka, HBase, etc. Hortonworks has certainly got the most up-to-date version of each component of Hadoop.

Compared to the other Hadoop distributions, the Ambari server provides the user an easy way to manage, to administrate and to configure their cluster. Ambari also provides a single view that gives you the possibility to use different Hadoop components from the same web interface.

This product gives the possibility to the organization to easily and quickly install and configure a Hadoop cluster. With this cluster, the organization will be able to store and process their data and bring out some specificity on it. For example, unknown common points between their clients or key elements that will increase or decrease the churn of the client.

It would be interesting to have an easy way to implement multi-tenant for HDFS with federation. At the moment, you have to do it manually in command line.

Also, it needs to support having more than two HDFS namenodes. HDFS supports more than 2 namenodes, but Hortonworks doesn't.

I work with it in different projects and POCs for two years now.

The only issue that I had was when I tried to reinstall the software on every node. You have to manually clean up everything, as Hortonworks doesn’t provide the ability to perform a clean uninstall (software, library, log, configuration files, etc). In some case, it can generate some problems if the uninstall has not done correctly.

I never had to create a case at the support, so I don’t know. I always find the answers to my questions on the web (forum or blog). There’s a big community that can support you.

I also used Cloudera, MapR, and Microsoft HD Insight.

The first time, I didn’t know anything about Big Data and Hadoop, so yes it was difficult because I did not clearly understand what I was doing.

The implementation was at the clients datacenter. My advice is to perform a POC on premise or via a virtual machine to learn how to use it and how to tune the configuration of each Hadoop component.

When implementing it in production, firstly you need to have a clear view of the requirements you need to perform the install. For example, if you are using a local repository to install the software, it has to be updated with Hortonworks sources, especially if there are security rules (firewall access, root access limitation, etc.).

My last piece of advice is that if you have a heavy load, it is really important to implement the solution on premise, not in a virtualized environment. If you do both, you will see the difference in performance.

The use of Hortonworks is free there’s no license but if you want there’s a support. It’s up to you to see if you need it (certainly) and to maybe negotiate it.

I did not really made the choice, as the client made it dependent on their experience, functionality of each distribution, privacy of the data and the licensing/support price.

Firstly perform a POC to learn and to get an idea of the load of your future applications. Then, you should be able to correctly design the need infrastructure.