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. Databases
  5. Presto vs Vertica

Presto vs Vertica

OverviewDecisionsComparisonAlternatives

Overview

Vertica
Vertica
Stacks90
Followers120
Votes16
Presto
Presto
Stacks394
Followers1.0K
Votes66

Presto vs Vertica: What are the differences?

Introduction

Presto and Vertica are two popular platforms used for data processing and analytics. While both have similar functionalities, they differ in several key aspects that make them ideal for specific use cases. In this article, we will explore six key differences between Presto and Vertica.

  1. Architecture: Presto is designed as a distributed SQL query engine that operates on a cluster of machines. It follows a federated architecture, where multiple nodes work together to process queries. On the other hand, Vertica adopts a massively parallel processing (MPP) architecture, where data is divided across multiple nodes for parallel query execution.

  2. Data Storage: Presto is designed to work with various data sources, including relational databases, Hadoop, and cloud storage systems like S3. It can access data in different formats, such as CSV, JSON, and Parquet. In contrast, Vertica uses its proprietary columnar storage format, optimized for efficient analytics and compression. It offers high-performance analytics on massive volumes of data.

  3. Query Optimization: Presto applies optimization techniques during the query runtime to provide faster results. It uses cost-based optimization, enabling it to choose the most efficient execution plan dynamically. Vertica, on the other hand, focuses heavily on query optimization during the compilation phase. It compiles and optimizes queries in advance, resulting in faster execution for complex analytical workloads.

  4. Concurrency and Scalability: Presto is designed to handle large-scale data processing with high concurrency. It scales horizontally by adding more worker nodes to the cluster, allowing it to execute queries in parallel. Vertica, on the other hand, is designed to be both concurrent and scalable. It efficiently utilizes hardware resources and supports workload management policies to prioritize different query workloads.

  5. Advanced Analytics: Presto primarily focuses on providing fast and interactive SQL queries, making it an ideal choice for ad hoc analysis and exploration. It supports basic analytical functions but lacks extensive built-in support for advanced analytics like machine learning algorithms. Vertica, on the contrary, offers a wide range of built-in analytical functions and supports machine learning capabilities. It provides a comprehensive analytics platform for complex analytical workloads.

  6. Cost and Licensing: Presto is open-source software with no licensing costs, making it an attractive option for organizations with limited budgets. It is maintained by a community of contributors, ensuring continuous improvement. Vertica, on the other hand, is a commercial product and requires licensing. It offers enterprise-level support and additional features that may be beneficial for organizations with specific requirements.

In summary, Presto and Vertica differ in their underlying architecture, data storage approaches, query optimization strategies, concurrency and scalability capabilities, support for advanced analytics, and cost/licensing models. Organizations should evaluate their specific requirements and use cases to choose the platform that best aligns with their needs.

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 Vertica, Presto

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

Vertica
Vertica
Presto
Presto

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

Distributed SQL Query Engine for Big Data

Analyze All of Your Data. No longer move data or settle for siloed views;Achieve Scale and Performance;Fear of growing data volumes and users is a thing of the past;Future-Proof Your Analytics
-
Statistics
Stacks
90
Stacks
394
Followers
120
Followers
1.0K
Votes
16
Votes
66
Pros & Cons
Pros
  • 3
    Shared nothing or shared everything architecture
  • 1
    Vertica is the only product which offers partition prun
  • 1
    Query-Optimized Storage
  • 1
    Fully automated Database Designer tool
  • 1
    Near-Real-Time Analytics in pure Column Store
Pros
  • 18
    Works directly on files in s3 (no ETL)
  • 13
    Open-source
  • 12
    Join multiple databases
  • 10
    Scalable
  • 7
    Gets ready in minutes
Integrations
Oracle
Oracle
Golang
Golang
MongoDB
MongoDB
MySQL
MySQL
Sass
Sass
Mode
Mode
PowerBI
PowerBI
Tableau
Tableau
Talend
Talend
PostgreSQL
PostgreSQL
Kafka
Kafka
Redis
Redis
MySQL
MySQL
Hadoop
Hadoop
Microsoft SQL Server
Microsoft SQL Server

What are some alternatives to Vertica, Presto?

MongoDB

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

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