Presto vs. Scality ARTESCA

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

The team in charge of implementing Scality has to be full stack in order to guarantee the correct functioning of the entire system. However, you have to think very carefully about the balance between servers and disks, perhaps adopting smaller fully populated servers instead of large semi-populated servers, which would mean that over time our disk updates will not have a fully useful life.

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

• I love the redundancy of the software.

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

• The overall packaging is not very good. I think it could be more efficient for installation.
• There are many components in storage servers. This can generally be complex to understand, you have to be patient.

Incentivized

As an organization, it took us a while to understand the shift from a traditional black box SAN to software-defined storage, but now we are much more certain of what this means. The time invested and the resources were not very high, thanks on the one hand to the technical support and on the other to the coherence and good development of the platform.

Incentivized

I have seen Scality in the office meeting with our VP and get the feeling that they are here to support us.

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

Due to the nature of our business we require extensive encryption and availability for sensitive customer data. The erasure encoding that Scality provides gives us the assurance that documents are rest are never in a state of being downloaded or available to a casual data thief. This is something that can be found with other vendors but at a fraction of the same cost. Having this kind of performance, availability and redundancy at the cost that Scality provides has made a large difference to our organization.

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

• Keeping sensitive customer data secure is a must for our organization and Scality has great features to make this happen.
• We replaced a single SAN with a Scality ring and found performance to improve as we store more and more customer data.
• Being able to lose various portions of our Scality ring and allow it to continue to service customers while maintaining high performance has been key to our business.

Incentivized