Apache Hive vs. Azure Data Lake Storage

Apache Hive shines for ad-hoc analysis and plugging into BI tools. Its SQL-like syntax allows for ease of use not for only for engineers but also for data analysts. Through our experience, there are probably more desirable tools to use if you are planning on integrating Hive into your processing pipeline.

Incentivized

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

• Hive syntax is almost like SQL, so for someone already familiar with SQL it takes almost no effort to pick up Hive.
• To be able to run map reduce jobs using json parsing and generate dynamic partitions in parquet file format.
• Simplifies your experience with Hadoop especially for non-technical/coding partners.

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

• Use Hive for analytical work loads. Write once and read many scenarios. Do not prefer updates and deletes.
• Behind scenes Hive creates map reduce jobs. Hive performance is slow compared to Apache Spark.
• Map reduce writes the intermediate outputs to dial whereas Spark operates in in-memory and uses DAG.

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

Since I do not know the second data warehouse solution that integrate with HDFS as well as Hive.

Hive is a very good big data analysis and ad-hoc query platform, which supports scaling also. The BI processes can be easily integrated with Hadoop via the Hive. It can deal with a much larger data set that traditional RDBMS can not. It is a "must-have" component of the big data domain.

Incentivized

Apache Hive is a FOSS project and its open source. We need not definitely comment on anything about the support of open source and its developer community. But, it has got tremendous developer support, awesome documentation. I would justify the fact that much support can be gathered from the community backup.

Incentivized

We have used a simple but necessary function such as merging certain data tables, which although they may be from different areas, complement each other or are necessary, you can use metadata if what you need is to validate the origin of your information and what impact it has, is also feasible.

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

• Good ROI for being able to access data easily across the network, we have large amounts of data and this is a good system to access it
• Good ROI for being easy to learn how to use for new employees, not much time spent which saves costs
• Good ROI for being able to integrate with Spark and other applications, hence data can be analyzed through programs

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