Need advice about which tool to choose?Ask the StackShare community!
Apache Hive vs Snowflake: What are the differences?
Introduction
Apache Hive and Snowflake are both popular tools used for data warehousing and analytics. While they both serve similar purposes, there are some key differences between these two platforms.
Data Warehousing Approach: Apache Hive is based on the Hadoop ecosystem and follows a traditional on-premises approach to data warehousing. It allows users to query and analyze large datasets stored in distributed file systems like HDFS. On the other hand, Snowflake is a cloud-based data warehousing platform that offers scalable and elastic storage and compute resources. It provides a service-based approach to data warehousing, allowing users to focus on analysis rather than infrastructure management.
Query Language: Apache Hive uses HiveQL, which is a SQL-like declarative language. It allows users to write SQL queries to analyze data stored in Hive. In contrast, Snowflake supports multiple query languages including standard SQL, which makes it easier for users familiar with SQL to get started. Snowflake also introduces some unique syntax and features, such as variant data type and semi-structured data support, which enable powerful querying capabilities.
Performance Optimization: Apache Hive relies on MapReduce for query processing, which can be slower when dealing with large datasets. Hive provides techniques like data partitioning and bucketing to improve query performance. Snowflake, on the other hand, utilizes a unique architecture that separates storage and compute layers. This allows for independent scalability and parallelism, resulting in faster query processing, especially for complex queries and large datasets.
Concurrency and Multi-Tenancy: Apache Hive supports multiple users and concurrent queries, but it may face contention issues when the number of concurrent users or queries increases. It requires external tools like YARN for resource management and scheduling. Snowflake, on the other hand, is built with multi-tenancy in mind. It automatically manages resource allocation and provides isolation between different accounts, ensuring consistent performance and preventing one user's workload from impacting others.
Data Sharing and Collaboration: Apache Hive provides features like Metastore and HCatalog that allow sharing and collaboration between different data processing frameworks, such as Pig and Spark. It also supports integration with other tools in the Hadoop ecosystem. Snowflake offers secure data sharing capabilities that allow organizations to share data with external parties without having to physically copy or move the data. It provides granular control over data access and allows users to share subsets of data or entire databases.
Deployment and Infrastructure Management: Apache Hive requires manual setup and configuration of the Hadoop ecosystem, including HDFS, YARN, and Hive itself. It requires expertise in managing and operating distributed systems. Snowflake, being a cloud-based service, eliminates the need for infrastructure management. It handles tasks like data replication, backup, and disaster recovery automatically, providing a hassle-free experience for users.
In summary, Apache Hive is a traditional on-premises data warehousing solution based on the Hadoop ecosystem, while Snowflake is a cloud-based data warehousing platform with a service-based approach. Snowflake offers better performance, scalability, and ease of use compared to Apache Hive, but Hive provides compatibility with other Hadoop tools and frameworks.
To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.
Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.
We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.
Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.
Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.
#BigData #AWS #DataScience #DataEngineering
The platform deals with time series data from sensors aggregated against things( event data that originates at periodic intervals). We use Cassandra as our distributed database to store time series data. Aggregated data insights from Cassandra is delivered as web API for consumption from other applications. Presto as a distributed sql querying engine, can provide a faster execution time provided the queries are tuned for proper distribution across the cluster. Another objective that we had was to combine Cassandra table data with other business data from RDBMS or other big data systems where presto through its connector architecture would have opened up a whole lot of options for us.
Pros of Apache Hive
Pros of Snowflake
- Public and Private Data Sharing7
- Multicloud4
- Good Performance4
- User Friendly4
- Great Documentation3
- Serverless2
- Economical1
- Usage based billing1
- Innovative1