Presto is an open source SQL query engine designed to run queries on data stored in Hadoop or in traditional databases.
Teradata supported development of Presto followed the acquisition of Hadapt and Revelytix.
N/A
Qlik Talend Cloud
Score 8.8 out of 10
N/A
The Qlik Talend Cloud suite of solutions offer data integration, data quality, application integration, and data governance that work with key data sources, targets, architectures, or methodologies to ensure business users always have trusted and accurate data.
N/A
Pricing
Presto
Qlik Talend Cloud
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Presto
Qlik Talend Cloud
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Presto
Qlik Talend Cloud
Features
Presto
Qlik Talend Cloud
Data Source Connection
Comparison of Data Source Connection features of Product A and Product B
Presto
-
Ratings
Qlik Talend Cloud
9.5
10 Ratings
14% above category average
Connect to traditional data sources
00 Ratings
10.010 Ratings
Connecto to Big Data and NoSQL
00 Ratings
9.09 Ratings
Data Transformations
Comparison of Data Transformations features of Product A and Product B
Presto
-
Ratings
Qlik Talend Cloud
9.0
10 Ratings
10% above category average
Simple transformations
00 Ratings
9.010 Ratings
Complex transformations
00 Ratings
9.010 Ratings
Data Modeling
Comparison of Data Modeling features of Product A and Product B
Presto
-
Ratings
Qlik Talend Cloud
9.0
10 Ratings
13% above category average
Data model creation
00 Ratings
9.09 Ratings
Metadata management
00 Ratings
10.09 Ratings
Business rules and workflow
00 Ratings
8.08 Ratings
Collaboration
00 Ratings
9.09 Ratings
Testing and debugging
00 Ratings
9.010 Ratings
Data Governance
Comparison of Data Governance features of Product A and Product B
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
This tool fits all kinds of organizations and helps to integrate data between many applications. We can use this tool as data integration is a key feature for all organizations. It is also available in the cloud, which makes the integration more seamless. The firm can opt for the required tools when there are no data integration needs.
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.
Talend Data Integration allows us to quickly build data integrations without a tremendous amount of custom coding (some Java and JavaScript knowledge is still required).
I like the UI and it's very intuitive. Jobs are visual, allowing the team members to see the flow of the data, without having to read through the Java code that is generated.
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.
We use Talend Data Integration day in and day out. It is the best and easiest tool to jump on to and use. We can build a basic integration super-fast. We could build basic integrations as fast as within the hour. It is also easy to build transformations and use Java to perform some operations.
Good support, specially when it relates to PROD environment. The support team has access to the product development team. Things are internally escalated to development team if there is a bug encountered. This helps the customer to get quick fix or patch designed for problem exceptions. I have also seen support showing their willingness to help develop custom connector for a newly available cloud based big data solution
Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.
In comparison with the other ETLs I used, Talend is more flexible than Data Services (where you cannot create complex commands). It is similar to Datastage speaking about commands and interfaces. It is more user-friendly than ODI, which has a metadata point of view on its own, while Talend is more classic. It has both on-prem and cloud approaches, while Matillion is only cloud-based.
It’s only been a positive RoI with Talend given we’ve interfaced large datasets between critical on-Prem and cloud-native apps to efficiently run our business operations.