Denodo vs. Presto vs. Toad Data Modeler

Denodo allows us to create and combine new views to create a
virtual repository and APIs without a single line of code. It is excellent
because it can present connectors with a view format for downstream consumers
by flattening a JSON file. Reading or connecting to various sources and
displaying a tabular view is an excellent feature. The product's technical data
catalog is well-organized.

Incentivized

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

Incentivized

• Database Agnostic: You can easily connect to different environments and mash up data sets.
• The "magic" of data virtualization: No data is created, so data is reported in near-real-time to end users.
• It's easy to use UI for developers. You just connect to a data source, create tables, and join them to other datasets.

Incentivized

• 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.

Incentivized

• Caching - but I am sure it will be improved by now. There were times when we expected the cache to be refreshed but it was stale.
• Schema generation of endpoints from API response was sometimes incomplete as not all API calls returned all the fields. Will be good to have an ability to load the schema itself (XSD/JSON/Soap XML etc).
• Denodo exposed web services were in preliminary stage when we used; I'm sure it will be improved by now.
• Export/Import deployment, while it was helpful, there were unexpected issues without any errors during deployment. Issues were only identified during testing. Some views were not created properly and did not work. If it was working in the environment from where it was exported from, it should work in the environment where it is imported.

Incentivized

• 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.

Incentivized

Denodo is very easy to use. It has a user-friendly drag and drop interface. I'm not a fan of the java platform it resides on.

Incentivized

Denodo is a tool to rapidly mash data sources together and create meaningful datasets. It does have its downfalls though. When you create larger, more complex datasets, you will most likely need to cache your datasets, regardless of how proper your joins are set up. Since DV takes data from multiple environments, you are taxing the corporate network, so you need to be conscious of how much data you are sending through the network and truly understand how and when to join datasets due to this.

Incentivized

Denodo is simple and easy to use. Highly recommended unless you have huge volumes of data

Incentivized

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.

Incentivized

• It is a huge advantage that we can connect to many different databases to provide data rapidly and accurately.
• It has proven to be a valuable environment for deploying data virtualization solutions, and its user community is active in finding and fixing issues.

Incentivized

• Presto has helped scale Uber's interactive data needs. We have migrated a lot out of proprietary tech like Vertica.
• Presto has helped build data driven applications on its stack than maintain a separate online/offline stack.
• Presto has helped us build data exploration tools by leveraging it's power of interactive and is immensely valuable for data scientists.

Incentivized