Cloudera Distribution Hadoop (CDH) vs. HPE Ezmeral Data Fabric (MapR)

Cloudera Distribution Hadoop (CDH) does a lot of things really well - especially on the analytical front. That being said the product is quite expensive. There are seemingly numerous applications that do the same thing on the functional level that are much more cost effecient for enterprise teams. If I were recommending this to a colleague I would let them know the product will absolutely be able to get the job done for their use case, but there are more efficient options

Incentivized

MapR is more well-suited for people who know what they are doing. I consider MapR the Hadoop distribution professionals use.

Incentivized

• Solid and robust set of integrations
• Easy to use and easy to deploy across the enterprise
• Reliability - never lost any info
• Simple and clean interface

Incentivized

• MapR had very fast I/O throughput. The write speed was several times faster than what we could achieve with the other Hadoop vendors (Cloudera and Hortonworks). This is because MapR does not use HDFS, which is essentially a "meta filesystem". HDFS is built on top of the filesystem provided by the OS. MapR has their filesystem called MapR-FS, which is a true filesystem and accesses the raw disk drives.
• The MapR filesystem is very easy to integrate with other Linux filesystems. When working with HDFS from Apache Hadoop, you usually have to use either the HDFS API or various Hadoop/HDFS command line utilities to interact with HDFS. You cannot use command line utilities native to the host operation system, which is usually Linux. At least, it is not easily done without setting up NFS, gateways, etc. With MapR-FS, you can mount the filesystem within Linux and use the standard Unix commands to manipulate files.
• The HBase distribution provided by MapR is very similar to the Apache HBase distribution. Cloudera and Hortonworks add GUIs and other various tools on top of their HBase distributions. The MapR HBase distribution is very similar to the Apache distribution, which is nice if you are more accustomed to using Apache HBase.

Incentivized

• The price is quite high competitively speaking
• Hard to learn more robust functions and custom options without experience

Incentivized

• It takes time to get latest versions of Apache ecosystem tools released as it has to be adapted.
• When you have issues related to Mapr-FS or Mapr Tables, its hard to figure them out by ourselves.
• Sometime new ecosystem tools versions are released without proper QA.

Incentivized

In terms of functionality there's not much difference, both get the job done. Amazon was more cost-efficient for our team, but this could vary depending on the size of the business. One thing I did notice was that Cloudera seemed to management and spit out our deployments faster than AWS.

Incentivized

I don't believe there is as much support for MapR yet compared to other more widely known products.

Incentivized

• Saves time by automating typically manual processes (data management, lifecyle AI etc)
• Quick deployments and analytics allow for faster time-to-value

Incentivized

• Increased employee efficiency for sure. Our clients have various levels of expertise in their deployment and user teams, and we never receive complaints about MapR.
• MapR is used by one of our financial services clients who uses it for fraud detection and user pattern analysis. They are able to turn around data much faster than they previously had with in-house applications

Incentivized