Azure Data Lake Storage vs. HPE Data Fabric

Azure Data Lake storage is well suited for applications/use cases within organizations where capturing and storing large amounts of data in any format is required, primarily for storing and processing purposes. It's an easy and cost-effective cloud solution for your application data. The ability to integrate with other Azure Services like Azure Databricks and Azure Data Factory is superb.

Incentivized

If you need Hadoop and just need raw speed for I/O and have a Hadoop savvy group of engineers who don't need/like web UIs, then MapR is a great fit for you. If you are new to Hadoop or have DevOps folks that are not Hadoop gurus, choosing MapR as your Hadoop vendor will have a steeper learning curve as you will need to do more training and build more admin consoles for them.

Incentivized

• Azure Data Lake Storage is extremely scalable. It allows us to scale up or down endlessly based on what we need including replication.
• In terms of security, Azure Data Lake Storage fits our requirements really well as we can monitor and encrypt seamlessly. We can also assign permissions through roles and grant network-level access.
• Due to the fact that it can scale, we are able to monitor the cost of storage and any given time and make financial decisions about our infrastructure based on how small or big we want to scale.

Incentivized

• MapR allows easy integration with HBase and MapR DB.
• Easy trial server setup for product testing.
• Excellent training program to help new users get up-to-date with MapR and related products.

Incentivized

• I'd like to see a better cross-platform native client. Azure Data Explorer is fine, but it's far from the "SSMS" kind of experience SQL Server users are used to.
• Listing a large number of file is somewhat problematic and slow. Using the native C# library, running directly on an Azure VM, it can take several hours to list just a couple million files.
• Switching from V1 to V2 requires the creation of a new Storage Account and that's pretty inconvenient.

Incentivized

• I think MapR's main problem is name recognition. Hortonworks and Cloudera both are big names in the industry, but their deployment mechanisms are a little more difficult to use, especially when trying to fully automate it's deployment.
• Documentation could always be better. But really, if that's your main weakness, it's everybody's weakness.

Incentivized

The Azure Data Lake solution is designed for organizations that want to take advantage of big data. It provides a data platform that can help developers, data scientists, and analysts store data of any size and format and perform all types of processing and analytics across multiple platforms and programming languages. It can work with your existing solutions, such as identity management and security solutions. It also integrates with other data warehouses and cloud environments. It can be useful for organizations that need the above softwares.

Incentivized

Hortonworks and Cloudera are both sort of hacky. We have to do a lot of extra steps to automate those two. MapR has far fewer issues and doesn't force you into a once size fits all deployment scenario. There are multiple ways to deploy and some are more amenable to automation, MapR just has that in spades

Incentivized

• The cost can be high for more advanced work. In some cases, for instance, time limits and lab runtimes may be too short if you are too slow to learn what is explained as you go along.
• promote flexible team communication. You can create different spaces for different teams, and share files and tasks.

Incentivized

• Less manual intervention for maintaining a cluster.

Incentivized