HPE Ezmeral Data Fabric (MapR) vs. SAP Vora

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

Incentivized

I spent more than 1 year with SAP Vora, SAP Datahub and SAP Leonardo with ML, iOt. I believe this product has potential but it is not easy to adopt. SAP has to keep in mind how open-source big data technologies are able to deliver quick results. I know SAP is stabilizing and fighting hard against many open source technologies, but it still has a long way to go there.

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

• Modelling with SAP HANA and Hadoop
• Realtime Analysis using Vora and HANA as a Streaming engine
• Time series Analysis on large chunks of datasets
• Machine learning capabilities on Hadoop tables and spark contexts

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

• Vora 2.0 in on premise scenarios could be improved, as adoption of the cloud is not an easy sell.
• Kubernetes and Docker integration need to be more seamless and quick to understand. If this is simplified, it will be easy to adopt
• Data hub orchestration and integrations could be simplified so that quick adoption within SAP BW, ECC, S4 HANa scenarios is possible.

Incentivized

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

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

• Negative impact would be Poc and RFI will need more time to adopt and decision making gets delayed
• Positive impact would be it's a great leap from SAP to adopt a Big data technologies and AI within cloud stream. But selling is going to take time.

Incentivized