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 Read full review I spent more than 1 year with SAP Vora, SAP Datahub and SAP Leonardo with ML, iOt. I believe this product has potential but it is not easy to adopt. SAP has to keep in mind how open-source big data technologies are able to deliver quick results. I know SAP is stabilizing and fighting hard against many open source technologies, but it still has a long way to go there.
Read full review 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. Read full review Modelling with SAP HANA and Hadoop Realtime Analysis using Vora and HANA as a Streaming engine Time series Analysis on large chunks of datasets Machine learning capabilities on Hadoop tables and spark contexts Read full review 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. Read full review Vora 2.0 in on premise scenarios could be improved, as adoption of the cloud is not an easy sell. Kubernetes and Docker integration need to be more seamless and quick to understand. If this is simplified, it will be easy to adopt Data hub orchestration and integrations could be simplified so that quick adoption within SAP BW, ECC, S4 HANa scenarios is possible. Read full review Alternatives Considered 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.
Read full review Return on Investment 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. Read full review Negative impact would be Poc and RFI will need more time to adopt and decision making gets delayed Positive impact would be it's a great leap from SAP to adopt a Big data technologies and AI within cloud stream. But selling is going to take time. Read full review ScreenShots