Apache Spark is a multi-language engine for executing data engineering, data science, and machine learning on single-node machines or clusters.
N/A
Everpure FlashBlade
Score 9.9 out of 10
N/A
Everpure (formerly Pure Storage) offers FlashBlade, a scale-out file and object storage – architected to consolidate complex data silos (like backup appliances and data lakes) while accelerating tomorrow's discoveries and insights.
N/A
Presto
Score 10.0 out of 10
N/A
Presto is an open source SQL query engine designed to run queries on data stored in Hadoop or in traditional databases.
Teradata supported development of Presto followed the acquisition of Hadapt and Revelytix.
All the above systems work quite well on big data transformations whereas Spark really shines with its bigger API support and its ability to read from and write to multiple data sources. Using Spark one can easily switch between declarative versus imperative versus functional …
I think Presto is one of the best solutions out there today at the cutting edge for interactive query analysis. One of the challenges is presto is a niche tool for the interactive query use case and doesn't have the knobs and whistles as much as Spark. In the foreseeable future …
Well suited: To most of the local run of datasets and non-prod systems - scalability is not a problem at all. Including data from multiple types of data sources is an added advantage. MLlib is a decently nice built-in library that can be used for most of the ML tasks. Less appropriate: We had to work on a RecSys where the music dataset that we used was around 300+Gb in size. We faced memory-based issues. Few times we also got memory errors. Also the MLlib library does not have support for advanced analytics and deep-learning frameworks support. Understanding the internals of the working of Apache Spark for beginners is highly not possible.
If data storage, access, and security [are] of the highest priority to your business then Pure Storage FlashBlade is an excellent tool that must be considered. Analytics or sharing that requires the fastest speeds available will benefit from the NVMe solid-state drives they use which are far superior to spinning rust. It is less ideal for those who do not require such time-critical work.
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
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.
When reporting out a user has exceeded there quote, it only references the UID. It would certainly be nice it calls out the UID name that is clearly present in the Dashboard.
The ability to determine a snapshot total size would be helpful.
Proactive reachout to discuss new versions and assist in planning the upgrade would be a key win.
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.
If the team looking to use Apache Spark is not used to debug and tweak settings for jobs to ensure maximum optimizations, it can be frustrating. However, the documentation and the support of the community on the internet can help resolve most issues. Moreover, it is highly configurable and it integrates with different tools (eg: it can be used by dbt core), which increase the scenarios where it can be used
1. It integrates very well with scala or python. 2. It's very easy to understand SQL interoperability. 3. Apache is way faster than the other competitive technologies. 4. The support from the Apache community is very huge for Spark. 5. Execution times are faster as compared to others. 6. There are a large number of forums available for Apache Spark. 7. The code availability for Apache Spark is simpler and easy to gain access to. 8. Many organizations use Apache Spark, so many solutions are available for existing applications.
Without exception, the contacts with support have been quick and extremely knowledgeable. I do not fear getting an underqualified engineer to assess or work on my arrays. In addition to this support structure, the sales engineers are top notch as well.
Spark in comparison to similar technologies ends up being a one stop shop. You can achieve so much with this one framework instead of having to stitch and weave multiple technologies from the Hadoop stack, all while getting incredibility performance, minimal boilerplate, and getting the ability to write your application in the language of your choosing.
The NetApp a800 we tested was 14% faster than Pure FlashBlade with NFS workloads. However, NetApp lacked ease of administration and performing simple tasks such as creating multiple NFS volumes required scripting from the command line. Our flashblade contained 15 baldes and our NetApp was a clustered pair with each half containing 24 nvme devices.
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.
We were able to consolidate 5 different storage platforms of lesser performance onto a single Flashblade and achieve much, much lower latency and higher throughput.
We've been able to reduce the amount of training and configuration required to just Pure Flashblade, instead of 5 different vendors and products.
In addition to our core use cases, Flashblade has capabilities that we are pursuing for some new projects, i.e. analytics data store and the object store features.
