Need advice about which tool to choose?Ask the StackShare community!

Presto

393
1K
+ 1
66
Apache Spark

3K
3.5K
+ 1
140
Add tool

Apache Spark vs Presto: What are the differences?

Introduction

Apache Spark and Presto are both popular open-source distributed query engines used for processing big data. While they serve a similar purpose, there are key differences between the two.

  1. Memory Management: Apache Spark uses a combination of in-memory caching and disk-based storage to manage data. It provides a resilient distributed dataset (RDD) abstraction for efficient and fault-tolerant processing. On the other hand, Presto relies solely on in-memory processing, making it faster but requiring more memory resources.

  2. Processing Engine: Spark uses a batch processing engine, where data is processed in small batches, allowing it to handle large volumes of data efficiently. Presto, on the other hand, uses a distributed SQL query engine, making it more suitable for interactive queries and ad-hoc analysis.

  3. Language Support: Spark provides built-in support for multiple programming languages, including Scala, Java, Python, and R, making it more versatile. Presto, on the other hand, primarily focuses on SQL and does not provide extensive language support for other programming languages.

  4. Data Sources: Spark supports a wide range of data sources, including Hadoop Distributed File System (HDFS), Apache Cassandra, Apache HBase, and more. Presto also supports multiple data sources, including HDFS, Amazon S3, MySQL, PostgreSQL, and many others. However, Spark's ecosystem is more mature and provides better integration with various data sources.

  5. Optimization Techniques: Spark incorporates several optimization techniques, such as query optimization, predicate pushdown, and data partitioning, to improve query performance. Presto also incorporates similar optimization techniques but focuses more on query parallelism and dynamic partition pruning.

  6. Scalability and Architecture: Spark is designed to scale horizontally and can handle massive amounts of data. It uses a master/worker architecture, where the master node manages the distribution of tasks to worker nodes. Presto, on the other hand, uses a distributed architecture with a coordinator and multiple worker nodes, allowing it to handle large-scale clusters efficiently.

In summary, Apache Spark and Presto differ in memory management, processing engine, language support, data sources, optimization techniques, and scalability/architecture. While Spark offers more versatility and a mature ecosystem, Presto excels in fast in-memory processing and interactive query capabilities.

Advice on Presto and Apache Spark
Nilesh Akhade
Technical Architect at Self Employed · | 5 upvotes · 516.5K views

We have a Kafka topic having events of type A and type B. We need to perform an inner join on both type of events using some common field (primary-key). The joined events to be inserted in Elasticsearch.

In usual cases, type A and type B events (with same key) observed to be close upto 15 minutes. But in some cases they may be far from each other, lets say 6 hours. Sometimes event of either of the types never come.

In all cases, we should be able to find joined events instantly after they are joined and not-joined events within 15 minutes.

See more
Replies (2)
Recommends
on
ElasticsearchElasticsearch

The first solution that came to me is to use upsert to update ElasticSearch:

  1. Use the primary-key as ES document id
  2. Upsert the records to ES as soon as you receive them. As you are using upsert, the 2nd record of the same primary-key will not overwrite the 1st one, but will be merged with it.

Cons: The load on ES will be higher, due to upsert.

To use Flink:

  1. Create a KeyedDataStream by the primary-key
  2. In the ProcessFunction, save the first record in a State. At the same time, create a Timer for 15 minutes in the future
  3. When the 2nd record comes, read the 1st record from the State, merge those two, and send out the result, and clear the State and the Timer if it has not fired
  4. When the Timer fires, read the 1st record from the State and send out as the output record.
  5. Have a 2nd Timer of 6 hours (or more) if you are not using Windowing to clean up the State

Pro: if you have already having Flink ingesting this stream. Otherwise, I would just go with the 1st solution.

See more
Akshaya Rawat
Senior Specialist Platform at Publicis Sapient · | 3 upvotes · 361.2K views
Recommends
on
Apache SparkApache Spark

Please refer "Structured Streaming" feature of Spark. Refer "Stream - Stream Join" at https://spark.apache.org/docs/latest/structured-streaming-programming-guide.html#stream-stream-joins . In short you need to specify "Define watermark delays on both inputs" and "Define a constraint on time across the two inputs"

See more
Decisions about Presto and Apache Spark
Ashish Singh
Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 2.8M views

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

See more
Karthik Raveendran
CPO at Attinad Software · | 3 upvotes · 207.6K views

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Presto
Pros of Apache Spark
  • 18
    Works directly on files in s3 (no ETL)
  • 13
    Open-source
  • 12
    Join multiple databases
  • 10
    Scalable
  • 7
    Gets ready in minutes
  • 6
    MPP
  • 61
    Open-source
  • 48
    Fast and Flexible
  • 8
    One platform for every big data problem
  • 8
    Great for distributed SQL like applications
  • 6
    Easy to install and to use
  • 3
    Works well for most Datascience usecases
  • 2
    Interactive Query
  • 2
    Machine learning libratimery, Streaming in real
  • 2
    In memory Computation

Sign up to add or upvote prosMake informed product decisions

Cons of Presto
Cons of Apache Spark
    Be the first to leave a con
    • 4
      Speed

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is Presto?

    Distributed SQL Query Engine for Big Data

    What is 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.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention Presto and Apache Spark as a desired skillset
    What companies use Presto?
    What companies use Apache Spark?
    See which teams inside your own company are using Presto or Apache Spark.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Presto?
    What tools integrate with Apache Spark?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Mar 24 2021 at 12:57PM

    Pinterest

    GitJenkinsKafka+7
    3
    2124
    MySQLKafkaApache Spark+6
    2
    1999
    Aug 28 2019 at 3:10AM

    Segment

    PythonJavaAmazon S3+16
    7
    2551
    What are some alternatives to Presto and Apache Spark?
    Stan
    A state-of-the-art platform for statistical modeling and high-performance statistical computation. Used for statistical modeling, data analysis, and prediction in the social, biological, and physical sciences, engineering, and business.
    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.
    Snowflake
    Snowflake eliminates the administration and management demands of traditional data warehouses and big data platforms. Snowflake is a true data warehouse as a service running on Amazon Web Services (AWS)—no infrastructure to manage and no knobs to turn.
    Apache Drill
    Apache Drill is a distributed MPP query layer that supports SQL and alternative query languages against NoSQL and Hadoop data storage systems. It was inspired in part by Google's Dremel.
    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.
    See all alternatives