Cloudera Distribution Hadoop (CDH) vs. Presto

Cloudera Distribution Hadoop (CDH) does a lot of things really well - especially on the analytical front. That being said the product is quite expensive. There are seemingly numerous applications that do the same thing on the functional level that are much more cost effecient for enterprise teams. If I were recommending this to a colleague I would let them know the product will absolutely be able to get the job done for their use case, but there are more efficient options

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

• Solid and robust set of integrations
• Easy to use and easy to deploy across the enterprise
• Reliability - never lost any info
• Simple and clean interface

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

• The price is quite high competitively speaking
• Hard to learn more robust functions and custom options without experience

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

In terms of functionality there's not much difference, both get the job done. Amazon was more cost-efficient for our team, but this could vary depending on the size of the business. One thing I did notice was that Cloudera seemed to management and spit out our deployments faster than AWS.

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

• Saves time by automating typically manual processes (data management, lifecyle AI etc)
• Quick deployments and analytics allow for faster time-to-value

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