Presto vs. Red Hat JBoss Data Virtualization

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

Red Hat JBoss Enterprise Data Services is a top choice for JEE applications. Even though lots of documentation is available, it's difficult in terms of usability. If the development is more based on Java applications it is a good choice. It provides better installation and integrations.

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

• Data source compatibility: since it is Java, it can connect to anything with a JDBC driver.
• Flexibility: you can configure it however you want, we have it configured to use LDAPS for authentication and have all interfaces encrypted, and setting that up was pretty straight forward.

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

• Pricing
• User Interface

Incentivized

Support availability and resolution response time make it a better choice.

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

Market value and support extended by Redhat is the winner against Veritas. It has cool features and functionality but still, if your organization is Redhat shop it's better to go for the Jboss option.

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

• It has allowed us to start moving applications independent from their underlying data sources, savings us time and limiting cutover effort.

Incentivized