Amazon EMR is a cloud-native big data platform for processing vast amounts of data quickly, at scale. Using open source tools such as Apache Spark, Apache Hive, Apache HBase, Apache Flink, Apache Hudi (Incubating), and Presto, coupled with the scalability of Amazon EC2 and scalable storage of Amazon S3, EMR gives analytical teams the engines and elasticity to run Petabyte-scale analysis.
N/A
IBM Analytics Engine
Score 7.1 out of 10
N/A
IBM BigInsights is an analytics and data visualization tool leveraging hadoop.
N/A
Pricing
Amazon EMR (Elastic MapReduce)
IBM Analytics Engine
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Amazon EMR
IBM Analytics Engine
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon EMR (Elastic MapReduce)
IBM Analytics Engine
Considered Both Products
Amazon EMR
Verified User
Anonymous
Chose Amazon EMR
Compared to IBM Analytics Engine, Amazon EMR is a much cheaper option to get the work down. And compared to Alluxio, Amazon EMR is much more user-friendly. The drawback is that amazon EMR would be very costly if the run failed.
We are running it to perform preparation which takes a few hours on EC2 to be running on a spark-based EMR cluster to total the preparation inside minutes rather than a few hours. Ease of utilization and capacity to select from either Hadoop or spark. Processing time diminishes from 5-8 hours to 25-30 minutes compared with the Ec2 occurrence and more in a few cases.
We are at present utilizing IBM Analytics Engine and it works incredible. Following are the things that I like the most about this product is:- - Simple to Utilize - Reasonable Cost - With only a couple seconds you can ready to fabricate and convey groups - you can without much of a stretch break down information through different applications
The cluster size of MapReduce is very dynamic and therefore scalability is good for EMR.
It also works well with other Amazon Web Services like Amazon Simple Storage Service, which means that data can be taken from those services and written back to them.
I tried using the in-house hosting at the university I work in, but there would be a lot of complications with technical support required. For Amazon, the support and documentation was good to solve these problems faster.
Sometimes bootstrapping certain tools comes with debugging costs. The tools provided by some of the enterprise editions are great compared to EMR.
Like some of the enterprise editions EMR does not provide on premises options.
No UI client for saving the workbooks or code snippets. Everything has to go through submitting process. Not really convenient for tracking the job as well.
Documentation is quite good and the product is regularly updated, so new features regularly come out. The setup is straightforward enough, especially once you have already established the overall platform infrastructure and the aws-cli APIs are easy enough to use. It would be nice to have some out-of-the-box integrations for checking logs and the Spark UI, rather than relying on know-how and digging through multiple levels to find the informations
I give the overall support for Amazon EMR this rating because while the support technicians are very knowledgeable and always able to help, it sometimes takes a very long time to get in contact with one of the support technicians. So overall the support is pretty good for Amazon EMR.
Snowflake is a lot easier to get started with than the other options. Snowflake's data lake building capabilities are far more powerful. Although Amazon EMR isn't our first pick, we've had an excellent experience with EC2 and S3. Because of our current API interfaces, it made more sense for us to continue with Hadoop rather than explore other options.
I have been using Azure for my previous analysis, I had a difficult time in understanding the Analytics engine rather IBM provided step by step tutorial for setup.
Also turning off a machine was not an option in Azure for some of the services so I had to pay for the service whether I use it or not
It was obviously cheaper and convenient to use as most of our data processing and pipelines are on AWS. It was fast and readily available with a click and that saved a ton of time rather than having to figure out the down time of the cluster if its on premises.
It saved time on processing chunks of big data which had to be processed in short period with minimal costs. EMR solved this as the cluster setup time and processing was simple, easy, cheap and fast.
It had a negative impact as it was very difficult in submitting the test jobs as it lags a UI to submit spark code snippets.
It has saved us quite a bit of time managing our catalog of clusters and keeping things organized.
Since we had a division we acquired running IBM Cloud, it was easy to get it running and try it out, but we found we prefer our Azure configuration better simply to keep our technology in alignment across corporate functions.
I definitely see some cost savings by separating out the storage and compute. It helps you start to put an appropriate price tag on certain instances of big data.
