Oracle Data Service Integrator vs. Presto

Once Oracle Data Service Integrator is set up properly, it is quite simple to snatch data from a myriad of disparate sources and put them into a single repository. Due to cost factors, it is not for the faint of heart; however, if you can handle it, the benefits will quickly outpace the initial investment. To take full advantage of the power of ODSI, I would recommend the training that Oracle provides.

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

• Very easy to use. Very easy to just grab data when needed.
• Very robust and has so many features to move and transform data.
• Functionality is very easy to implement with other Oracle data products.

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

• If not bundled with other products, the price can be prohibitively expensive
• SAP connectors tend to be a little expensive and slightly difficult to use
• The audit module had some difficulties debugging failed instances

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

While we tested and evaluated multiple data service providers, we came to choose Oracle Data Service Integrator since our infrastructure was so heavily dependent on Oracle software. The implementation would be easier and the difference in the number of features and performance wasn't enough to sway us in another direction.

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

• It provided terrific bulk data movement and data transformation services which we desperately needed
• It allowed to reduce development costs and lower the total cost of ownership among disparate architectures
• The enterprise edition's ELT allowed us to generate native code for wildly varied RDBMS

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