MySQL Heatwave vs. Presto

If you need a highly performant database, which is much faster than a conventional RDBMS, without worrying about infrastructure scaling, performance tuning, and query optimization, go for MySQL Heatwave. This is the best in the market. It is also very secure and reliable. Regular backups ensure that your data is safe and consistent always.

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

• Data mining
• Data analysis
• Parallel computing

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

• Pricing can be a concern if not configured properly
• Not available as a standalone or on premise offering. Only available through OCI
• No Jobs interface like that in Databricks with Spark and Delta Lake

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

We have not used other platforms. So, after a market survey on price, support and facilities, we have decided to go for MySQL Heatwave platform. Which integrates many technologies and provide best support, service and pricing. Also, it provides access to database. The speed of the execution is very high.

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

• We no longer have to write data pipelines in Spark anymore for executing ML/Analytics Workloads
• Execution time of the analytics platforms has reduced considerably
• Overall time to market has gone down drastically

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