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

PostgREST

50
101
+ 1
8
Presto

346
870
+ 1
64
Add tool

PostgREST vs Presto: What are the differences?

Developers describe PostgREST as "Automatic REST API for Any Postgres Database". PostgREST serves a fully RESTful API from any existing PostgreSQL database. It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch. On the other hand, Presto is detailed as "Distributed SQL Query Engine for Big Data". Presto is an open source distributed SQL query engine for running interactive analytic queries against data sources of all sizes ranging from gigabytes to petabytes.

PostgREST and Presto are primarily classified as "Database" and "Big Data" tools respectively.

PostgREST and Presto are both open source tools. PostgREST with 12.5K GitHub stars and 586 forks on GitHub appears to be more popular than Presto with 9.3K GitHub stars and 3.15K GitHub forks.

Decisions about PostgREST and Presto
Ashish Singh
Tech Lead, Big Data Platform at Pinterest · | 36 upvotes · 906.8K 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 · 136.3K 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 Private StackShare. Sign up for Private StackShare.
Learn More
Pros of PostgREST
Pros of Presto
  • 4
    Fast, simple, powerful REST APIs from vanilla Postgres
  • 2
    JWT authentication
  • 1
    Very fast
  • 1
    Declarative role based security at the data layer
  • 17
    Works directly on files in s3 (no ETL)
  • 13
    Open-source
  • 11
    Join multiple databases
  • 10
    Scalable
  • 7
    Gets ready in minutes
  • 5
    MPP

Sign up to add or upvote prosMake informed product decisions

What is PostgREST?

PostgREST serves a fully RESTful API from any existing PostgreSQL database. It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch.

What is Presto?

Distributed SQL Query Engine for Big Data

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

What companies use PostgREST?
What companies use Presto?
See which teams inside your own company are using PostgREST or Presto.
Sign up for Private StackShareLearn More

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

What tools integrate with PostgREST?
What tools integrate with Presto?

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

What are some alternatives to PostgREST and Presto?
GraphQL
GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012.
Slick
It is a modern database query and access library for Scala. It allows you to work with stored data almost as if you were using Scala collections while at the same time giving you full control over when a database access happens and which data is transferred.
Spring Data
It makes it easy to use data access technologies, relational and non-relational databases, map-reduce frameworks, and cloud-based data services. This is an umbrella project which contains many subprojects that are specific to a given database.
DataGrip
A cross-platform IDE that is aimed at DBAs and developers working with SQL databases.
Microsoft SQL Server Management Studio
It is an integrated environment for managing any SQL infrastructure, from SQL Server to Azure SQL Database. It provides tools to configure, monitor, and administer instances of SQL Server and databases. Use it to deploy, monitor, and upgrade the data-tier components used by your applications, as well as build queries and scripts.
See all alternatives