Likelihood to Recommend Well suited for my big data related project or a static data set analysis especially for uploading huge dataset to the cluster. But had some issues with connecting IoT real-time data and feeding to Power BI. It might be my understanding please take it as a mere comment rather than a suggestion. Read full review 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 Pros Jobs with Spark, Hadoop, or Hive queries are rapidly attained Can collect, organize and analyze your data accurately You can customize, for example, Spark or Hadoop configuration settings, or Python, R, Scala, or Java libraries. Read full review 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 Cons Easier pricing and plug-and-play like you see with AWS and Azure, it would be nice from a budgeting and billing standpoint, as well as better support for the administration. Bundling of the Cloud Object Storage should be included with the Analytics Engine. The inability to add your own Hadoop stack components has made some transfers a little more complex. Read full review 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 Alternatives Considered We initially wanted to go with
Google BigQuery , mainly for the name recognition. However, the pricing and support structure led us to seek alternatives, which pointed us to IBM.
Apache Spark was also in the running, but here IBM's domination in the industry made the choice a no-brainer. As previously stated, the support received was not quite what we expected, but was adequate.
Read full review 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 This product has allowed us to gather analytics data across multiple platforms so we can view and analyze the data from different workflows, all in one place. IBM Analytics has allowed us to scale on demand which allows us to capture more and more data, thus increasing our ROI. The convenience of the ability to access and administer the product via multiple interfaces has allowed our administrators to ensure that the application is making a positive ROI for our business users and partners. Read full review 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 ScreenShots