Amazon EMR (Elastic MapReduce) vs. IBM Watson Studio on Cloud Pak for Data

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.

Incentivized

It has a lot of features that are good for teams working on large-scale projects and continuously developing and reiterating their data project models. Really helpful when dealing with large data. It is a kind of one-stop solution for all data science tasks like visualization, cleaning, analyzing data, and developing models but small teams might find a lot of features unuseful.

Incentivized

• 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.

Incentivized

• Integration of IBM Watson APIs such as speech to text, image recognition, personality insights, etc.
• SPSS modeler and neural network model provide no-code environments for data scientists to build pipelines quickly.
• Enforced best-practices set up POCs for deployment in production with a minimum of re-work.
• Estimator validation lets data scientists test and prove different models.

Incentivized

• 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.

Incentivized

• The cost is steep and so only companies with resources can afford it
• It will be nice to have Chinese versions so that Chinese engineers can also use it easily
• It takes a while to learn how to input different kinds of skin defects for detection

Incentivized

because we find out that DSX results have improved our approach to the whole subject (data, models, procedures)

Incentivized

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

Incentivized

The UI flawlessly merges this offering by providing a neat, minimal, responsive interface

Incentivized

From time to time there are services unavailable, but we have been always informed before and they got back to work sooner than expected

Incentivized

Never had slow response even on our very busy network

Incentivized

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.

Incentivized

I received answers mostly at once and got answered even further my question: they gave me interesting points of view and suggestion for deepening in the learning path

Incentivized

The trainers on the job are very smart with solutions and very able in teaching

Incentivized

The Platform is very handy and suggests further steps according my previous interests

Incentivized

It surprised us with unpredictable case of use and brand new points of view

Incentivized

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.

Incentivized

The main reason I personally changed over from Azure ML Studio is because it lacked any support for significant custom modelling with packages and services such as TensorFlow, scikit-learn, Microsoft Cognitive Toolkit and Spark ML. IBM Watson Studio provides these services and does so in a well integrated and easy to use fashion making it a preferable service over the other services that I have personally used.

Incentivized

It helped us in getting from 0 to DSX without getting lost

Incentivized

• 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.

Incentivized

• Could instantly show data driven insights to drive 20% incremental revenue over existing results
• Still don't have a real use case for unstructured data like twitter feed
• Some of the insights around user actions have driven new projects to automate mundane tasks

Incentivized