Presto Reviews and Ratings

Rating: 10 out of 10

Score

10 out of 10

Community insights

TrustRadius Insights for Presto are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Fast Data Delivery: Many users have been amazed by the superfast query response of Presto, indicating its highly efficient handling of data queries.

Flexible Data Access: Users appreciate the flexibility of Presto in adapting to query translations and connecting with multiple data sources like HIVE and MySQL. This wide range of options for accessing and analyzing different types of data is highly valued by reviewers.

User-Friendly Interface: Reviewers find Presto to be a well-known SQL engine in the database industry, highlighting its organization and ease of querying data objects. The user-friendly interface and SQL syntax make it easy for users to work with Presto.

Reviews

2 Reviews

Why do we Presto

Rating: 8 out of 10

Incentivized

August 8, 2017

Use Cases and Deployment Scope

Presto is used at Uuber for ad-hoc querying on datasets and also for a few data driven applications. It is used across the entire organization to make data driven decisions, reporting, experimentation analysis etc. Presto provides a scalable, fast distributed query engine and we use it on top of HDFS.

Pros

Fast - Presto, is incredibly fast due to its optimized query engine and is well suited for interactive analysis.
Flexible - Presto is highly flexible as it operates with a plug and play model for data sources. Joining and query across different data sources is very easy with presto (eg. HDFS, MySQL, Kafka).
ANSI Sql - Presto follows ANSI SQL which is the recognized SQL language and hence helps allow easy query migration without much overhead.
Large Fact + Small Dimension table joins made fast - By design presto excels most distributed query engines out there in this type of queries.

Cons

Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem.
Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override.
UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc.

Likelihood to Recommend

Presto is for interactive simple queries, where Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like Vertica.

Praveen Murugesan

Engineering Manager - Ride Experience in Engineering at Uber (5001-10,000 employees)

Vetted Review

2 years of experience

View profile

Presto Review for Insider (Gannett)

Rating: 7 out of 10

Incentivized

March 23, 2017

Use Cases and Deployment Scope

Presto is used as our story publisher via The Des Moines Register and Gannett sites. We build, edit, and design story layout and publish to our website. My Marketing Group mainly uses Presto for our Insider program - this is a template of offers, deals & events exclusively for our subscribers.

Pros

Linking, embedding links and adding images is easy enough.
Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope).
Organizing & design is fairly simple with click & drag parameters.

Cons

HCI - Intuitively there are quite a few design elements I was unsure of before I got enough practice.
Curating Fronts - should have an auto-organize element so you don't need to move each front.
Save, Publish & Unpublish options should be easier to understand.
Presto should have a copy feature.

Likelihood to Recommend

Simple stories & templates work nicely - like for our Insider program.

Stories that include a lot of images may be challenging to create & have look appealing.

Corinne Nacin-Martinez

Consumer Sales & Sevice Manager in Marketing at Gannett (10,001+ employees)

Vetted Review

1 year of experience

View profile

Loading Reviews List....

Home
,
Relational Databases
,
Presto
,
Reviews and Ratings

Why do we Presto

Rating: 8 out of 10

Incentivized

August 8, 2017

Use Cases and Deployment Scope

Pros

Fast - Presto, is incredibly fast due to its optimized query engine and is well suited for interactive analysis.
Flexible - Presto is highly flexible as it operates with a plug and play model for data sources. Joining and query across different data sources is very easy with presto (eg. HDFS, MySQL, Kafka).
ANSI Sql - Presto follows ANSI SQL which is the recognized SQL language and hence helps allow easy query migration without much overhead.
Large Fact + Small Dimension table joins made fast - By design presto excels most distributed query engines out there in this type of queries.

Cons

Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem.
Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override.
UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc.

Likelihood to Recommend

Praveen Murugesan

Engineering Manager - Ride Experience in Engineering at Uber (5001-10,000 employees)

Vetted Review

2 years of experience

View profile