Need advice about which tool to choose?Ask the StackShare community!
Presto vs Snowflake: What are the differences?
Presto and Snowflake are both popular data warehousing platforms used for analyzing large volumes of data. While they share some similarities, there are key differences that set them apart.
1. Data Storage and Architecture: One major difference between Presto and Snowflake lies in their data storage and architecture. Presto is designed to query data stored in different storage systems, such as Hadoop Distributed File System (HDFS) or cloud storage services, making it a more versatile choice. On the other hand, Snowflake has its own native storage system, which offers better performance and scalability for data warehousing workloads.
2. SQL Dialect and Compatibility: Another difference lies in the SQL dialect and compatibility. Presto uses a standard SQL dialect with support for features commonly found in relational databases, making it easier for SQL developers to work with. Snowflake, while also offering ANSI SQL compatibility, has its own unique syntax and features, which may require some learning curve for developers transitioning from other platforms.
3. Query Optimization: Presto and Snowflake also differ in their approach to query optimization. Presto performs query optimization at runtime, analyzing data statistics and adding optimizations on the fly. This allows for more dynamic decision-making during query execution. On the other hand, Snowflake utilizes a cost-based optimizer that optimizes and compiles queries before execution, resulting in potentially faster and more consistent performance.
4. Data Protection and Security Features: When it comes to data protection and security, Snowflake offers advanced features such as automatic data encryption, granular access controls, and role-based access management. These features ensure secure data storage and prevent unauthorized access. While Presto can also be secured using external tools, it may require additional configuration and setup for implementing similar levels of security.
5. Scalability and Concurrency: Snowflake is known for its excellent scalability and concurrency capabilities. With its multi-cluster architecture, Snowflake can handle thousands of simultaneous queries efficiently, making it a suitable choice for organizations with large user bases and high concurrency requirements. While Presto is also scalable, it may require manual configuration and optimization to achieve optimal performance under high-concurrency scenarios.
6. Cost Model and Pricing: Lastly, Presto and Snowflake differ in their cost model and pricing structure. Presto is an open-source framework that can be freely used, making it a cost-effective option for organizations with limited budgets. Snowflake, on the other hand, follows a subscription-based pricing model, which includes different pricing tiers based on storage and compute resource usage. This can be advantageous for organizations that require predictable costs and prefer a pay-as-you-go approach.
In summary, Presto and Snowflake differ in terms of data storage and architecture, SQL dialect and compatibility, query optimization, data protection and security features, scalability and concurrency, as well as cost model and pricing structure. Organizations should carefully consider these differences when choosing between these two platforms, based on their specific requirements and use cases.
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 Presto
- Works directly on files in s3 (no ETL)18
- Open-source13
- Join multiple databases12
- Scalable10
- Gets ready in minutes7
- MPP6
Pros of Snowflake
- Public and Private Data Sharing7
- Multicloud4
- Good Performance4
- User Friendly4
- Great Documentation3
- Serverless2
- Economical1
- Usage based billing1
- Innovative1