StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Big Data Tools
  5. Delta Lake vs Presto

Delta Lake vs Presto

OverviewDecisionsComparisonAlternatives

Overview

Presto
Presto
Stacks394
Followers1.0K
Votes66
Delta Lake
Delta Lake
Stacks105
Followers315
Votes0
GitHub Stars8.4K
Forks1.9K

Delta Lake vs Presto: What are the differences?

Introduction

Delta Lake and Presto are two widely used technologies in the field of big data and analytics. While both serve similar purposes, they have some key differences that make them distinct from each other. In this article, we will explore these differences in detail.

  1. Data Storage and Processing: Delta Lake is an open-source storage layer that combines data lake and data warehousing capabilities. It stores data in Apache Parquet format and maintains transaction log files for its operations. On the other hand, Presto is a distributed SQL query engine that allows querying and processing of data across various data sources, including Hadoop Distributed File System (HDFS), Cassandra, and Elasticsearch. While Delta Lake focuses on storage and transaction management, Presto focuses on processing and querying.

  2. Data Consistency: Delta Lake provides ACID (Atomicity, Consistency, Isolation, Durability) transactions, which ensure data consistency and integrity. It allows multiple concurrent writers and provides transactional guarantees for data modification operations. In contrast, Presto does not provide built-in support for ACID transactions. It allows concurrent reads and writes but does not guarantee strong consistency for data modifications.

  3. Query Language: Delta Lake supports querying using traditional SQL, as well as Spark SQL, which extends SQL with additional features for working with structured and semi-structured data. On the other hand, Presto uses a subset of ANSI SQL for querying data, which is compatible with most SQL databases and allows users to write complex queries using standard SQL syntax.

  4. Data Catalog Integration: Delta Lake integrates well with Apache Hive, allowing users to query and manage Delta tables using Hive's metastore. It also supports integration with other data catalogs like AWS Glue and Databricks Data Catalog. On the other hand, Presto does not have its own data catalog but can integrate with external catalogs like Hive, Apache Cassandra, and PostgreSQL for accessing metadata and enabling table discovery.

  5. Performance Optimization: Delta Lake provides various performance optimization techniques like data skipping, predicate pushdown, and z-ordering, which improve query performance by reducing data scan and filtering operations. It also supports automatic and manual optimization of data layout for better query execution. Presto, on the other hand, optimizes query execution by pushing down filters and projections to the data source and using techniques like pipelining and parallelism. It also supports dynamic filtering to further improve performance.

  6. Scalability and Resource Management: Delta Lake can scale horizontally across multiple nodes and handle large volumes of data efficiently. It leverages distributed computing capabilities of Apache Spark for processing and analytics. Presto is designed to be highly scalable and can handle petabytes of data across thousands of nodes in a distributed cluster. It uses a sophisticated resource manager to allocate resources dynamically based on query requirements.

In summary, Delta Lake focuses on data storage, consistency, and transaction management, while Presto is a distributed SQL query engine that focuses on querying and processing data across various data sources. Delta Lake provides ACID transactions, supports SQL and Spark SQL, integrates well with data catalogs, provides performance optimization techniques, and scales horizontally using Apache Spark. Presto, on the other hand, supports a subset of ANSI SQL, integrates with external catalogs, optimizes query execution using filter pushdown and parallelism, and can scale to handle petabytes of data across a distributed cluster.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Presto, Delta Lake

Ashish
Ashish

Tech Lead, Big Data Platform at Pinterest

Nov 27, 2019

Needs adviceonApache HiveApache HivePrestoPrestoAmazon EC2Amazon EC2

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

3.72M views3.72M
Comments
Karthik
Karthik

CPO at Cantiz

Nov 5, 2019

Decided

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.

225k views225k
Comments

Detailed Comparison

Presto
Presto
Delta Lake
Delta Lake

Distributed SQL Query Engine for Big Data

An open-source storage layer that brings ACID transactions to Apache Spark™ and big data workloads.

-
ACID Transactions; Scalable Metadata Handling; Time Travel (data versioning); Open Format; Unified Batch and Streaming Source and Sink; Schema Enforcement; Schema Evolution; 100% Compatible with Apache Spark API
Statistics
GitHub Stars
-
GitHub Stars
8.4K
GitHub Forks
-
GitHub Forks
1.9K
Stacks
394
Stacks
105
Followers
1.0K
Followers
315
Votes
66
Votes
0
Pros & Cons
Pros
  • 18
    Works directly on files in s3 (no ETL)
  • 13
    Open-source
  • 12
    Join multiple databases
  • 10
    Scalable
  • 7
    Gets ready in minutes
No community feedback yet
Integrations
PostgreSQL
PostgreSQL
Kafka
Kafka
Redis
Redis
MySQL
MySQL
Hadoop
Hadoop
Microsoft SQL Server
Microsoft SQL Server
Apache Spark
Apache Spark
Hadoop
Hadoop
Amazon S3
Amazon S3

What are some alternatives to Presto, Delta Lake?

Apache Spark

Apache Spark

Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning.

Amazon Athena

Amazon Athena

Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run.

Apache Flink

Apache Flink

Apache Flink is an open source system for fast and versatile data analytics in clusters. Flink supports batch and streaming analytics, in one system. Analytical programs can be written in concise and elegant APIs in Java and Scala.

lakeFS

lakeFS

It is an open-source data version control system for data lakes. It provides a “Git for data” platform enabling you to implement best practices from software engineering on your data lake, including branching and merging, CI/CD, and production-like dev/test environments.

Druid

Druid

Druid is a distributed, column-oriented, real-time analytics data store that is commonly used to power exploratory dashboards in multi-tenant environments. Druid excels as a data warehousing solution for fast aggregate queries on petabyte sized data sets. Druid supports a variety of flexible filters, exact calculations, approximate algorithms, and other useful calculations.

Apache Kylin

Apache Kylin

Apache Kylin™ is an open source Distributed Analytics Engine designed to provide SQL interface and multi-dimensional analysis (OLAP) on Hadoop/Spark supporting extremely large datasets, originally contributed from eBay Inc.

Splunk

Splunk

It provides the leading platform for Operational Intelligence. Customers use it to search, monitor, analyze and visualize machine data.

Apache Impala

Apache Impala

Impala is a modern, open source, MPP SQL query engine for Apache Hadoop. Impala is shipped by Cloudera, MapR, and Amazon. With Impala, you can query data, whether stored in HDFS or Apache HBase – including SELECT, JOIN, and aggregate functions – in real time.

Vertica

Vertica

It provides a best-in-class, unified analytics platform that will forever be independent from underlying infrastructure.

Azure Synapse

Azure Synapse

It is an analytics service that brings together enterprise data warehousing and Big Data analytics. It gives you the freedom to query data on your terms, using either serverless on-demand or provisioned resources—at scale. It brings these two worlds together with a unified experience to ingest, prepare, manage, and serve data for immediate BI and machine learning needs.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase