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.3 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
Employee
Chose Amazon EMR (Elastic MapReduce)
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.
Well suited for my big data related project or a static data set analysis especially for uploading huge dataset to the cluster.
But had some issues with connecting IoT real-time data and feeding to Power BI. It might be my understanding please take it as a mere comment rather than a suggestion.
EMR does well in managing the cost as it uses the task node cores to process the data and these instances are cheaper when the data is stored on s3. It is really cost efficient. No need to maintain any libraries to connect to AWS resources.
EMR is highly available, secure and easy to launch. No much hassle in launching the cluster (Simple and easy).
EMR manages the big data frameworks which the developer need not worry (no need to maintain the memory and framework settings) about the framework settings. It's all setup on launch time. The bootstrapping feature is great.
It would have been better if packages like HBase and Flume were available with Amazon EMR. This would make the product even more helpful in some cases.
Products like Cloudera provide the options to move the whole deployment into a dedicated server and use it at our discretion. This would have been a good option if available with EMR.
If EMR gave the option to be used with any choice of cloud provider, it would have helped instead of having to move the data from another cloud service to S3.
Easier pricing and plug-and-play like you see with AWS and Azure, it would be nice from a budgeting and billing standpoint, as well as better support for the administration.
Bundling of the Cloud Object Storage should be included with the Analytics Engine.
The inability to add your own Hadoop stack components has made some transfers a little more complex.
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.
We initially wanted to go with Google BigQuery, mainly for the name recognition. However, the pricing and support structure led us to seek alternatives, which pointed us to IBM. Apache Spark was also in the running, but here IBM's domination in the industry made the choice a no-brainer. As previously stated, the support received was not quite what we expected, but was adequate.
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.
This product has allowed us to gather analytics data across multiple platforms so we can view and analyze the data from different workflows, all in one place.
IBM Analytics has allowed us to scale on demand which allows us to capture more and more data, thus increasing our ROI.
The convenience of the ability to access and administer the product via multiple interfaces has allowed our administrators to ensure that the application is making a positive ROI for our business users and partners.
