Try our new research platform with insights from 80,000+ expert users

AWS Batch vs Apache Spark comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Apache Spark
Ranking in Compute Service
4th
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
64
Ranking in other categories
Hadoop (1st), Java Frameworks (2nd)
AWS Batch
Ranking in Compute Service
6th
Average Rating
9.0
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of December 2024, in the Compute Service category, the mindshare of Apache Spark is 11.1%, up from 7.8% compared to the previous year. The mindshare of AWS Batch is 19.1%, down from 20.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Compute Service
 

Featured Reviews

SurjitChoudhury - PeerSpot reviewer
Offers batch processing of data and in-memory processing in Spark greatly enhances performance
Spark supports real-time data processing through Spark Streaming. It allows for batch processing of data. If you have immediate data, like chat information, that needs to be processed in real-time, Spark Streaming is used. For data that can be evaluated later, batch processing with Apache Spark is suitable. Mostly, batch processing is utilized in our organization, but for streaming data processing, tools like Kafka are often integrated. In-memory processing in Spark greatly enhances performance, making it a hundred times faster than the previous MapReduce methods. This improvement is achieved through optimization techniques like caching, broadcasting, and partitioning, which help in optimizing queries for faster processing.
Larry Singh - PeerSpot reviewer
User-friendly, good customization and offers exceptional scalability, allowing users to run jobs ranging from 32 cores to over 2,000 cores
The main drawback to using AWS Batch would be the cost. It will be more expensive in some cases than using an HPC. It's more amenable to cases where you have spot requirements. So, for instance, you don't exactly know how much compute resources you'll need and when you'll need them. So it's much better for that flexibility. But if you're going to be running jobs consistently and using the compute cluster consistently for a lot of time, and it's not going to have a lot of downtime, then the HPC system might be a better alternative. So, really, it boils down to cost versus usage trade-offs. It's going to be more expensive for a lot of people. In future releases, I would like to see anything that could help make it easier to set up your initial system. And besides improving the GUI a little bit, the interface to it, making it a little bit more descriptive and having more information at your fingertips, so if you could point to the help of what the different features are, you can get quick access to that. That might help. With most of the AWS services, the difficulty really is getting information and knowledge about the system and seeing examples. So, seeing examples of how it's being used under multiple use cases would be the best way to become familiar with it. And some of that would just come with experience. You have to just use it and play with it. But in terms of the system itself, it's not that difficult to set up or use.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"We use it for ETL purposes as well as for implementing the full transformation pipelines."
"The good performance. The nice graphical management console. The long list of ML algorithms."
"I like that it can handle multiple tasks parallelly. I also like the automation feature. JavaScript also helps with the parallel streaming of the library."
"With Hadoop-related technologies, we can distribute the workload with multiple commodity hardware."
"The features we find most valuable are the machine learning, data learning, and Spark Analytics."
"It's easy to prepare parallelism in Spark, run the solution with specific parameters, and get good performance."
"The most significant advantage of Spark 3.0 is its support for DataFrame UDF Pandas UDF features."
"The scalability has been the most valuable aspect of the solution."
"There is one other feature in confirmation or call confirmation where you can have templates of what you want to do and just modify those to customize it to your needs. And these templates basically make it a lot easier for you to get started."
"AWS Batch's deployment was easy."
"We can easily integrate AWS container images into the product."
"AWS Batch manages the execution of computing workload, including job scheduling, provisioning, and scaling."
 

Cons

"Apart from the restrictions that come with its in-memory implementation. It has been improved significantly up to version 3.0, which is currently in use."
"The migration of data between different versions could be improved."
"I know there is always discussion about which language to write applications in and some people do love Scala. However, I don't like it."
"For improvement, I think the tool could make things easier for people who aren't very technical. There's a significant learning curve, and I've seen organizations give up because of it. Making it quicker or easier for non-technical people would be beneficial."
"The solution must improve its performance."
"It requires overcoming a significant learning curve due to its robust and feature-rich nature."
"The initial setup was not easy."
"Technical expertise from an engineer is required to deploy and run high-tech tools, like Informatica, on Apache Spark, making it an area where improvements are required to make the process easier for users."
"The solution should include better and seamless integration with other AWS services, like Amazon S3 data storage and EC2 compute resources."
"AWS Batch needs to improve its documentation."
"The main drawback to using AWS Batch would be the cost. It will be more expensive in some cases than using an HPC. It's more amenable to cases where you have spot requirements."
"When we run a lot of batch jobs, the UI must show the history."
 

Pricing and Cost Advice

"The tool is an open-source product. If you're using the open-source Apache Spark, no fees are involved at any time. Charges only come into play when using it with other services like Databricks."
"The product is expensive, considering the setup."
"It is quite expensive. In fact, it accounts for almost 50% of the cost of our entire project."
"Apache Spark is not too cheap. You have to pay for hardware and Cloudera licenses. Of course, there is a solution with open source without Cloudera."
"Apache Spark is an open-source solution, and there is no cost involved in deploying the solution on-premises."
"It is an open-source solution, it is free of charge."
"I did not pay anything when using the tool on cloud services, but I had to pay on the compute side. The tool is not expensive compared with the benefits it offers. I rate the price as an eight out of ten."
"Considering the product version used in my company, I feel that the tool is not costly since the product is available for free."
"AWS Batch's pricing is good."
"AWS Batch is a cheap solution."
"The pricing is very fair."
report
Use our free recommendation engine to learn which Compute Service solutions are best for your needs.
824,067 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
27%
Computer Software Company
13%
Manufacturing Company
8%
Retailer
5%
Financial Services Firm
27%
Computer Software Company
12%
Manufacturing Company
7%
Government
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Apache Spark?
We use Spark to process data from different data sources.
What is your experience regarding pricing and costs for Apache Spark?
Compared to other solutions like Doc DB, Spark is more costly due to the need for extensive infrastructure. It requires significant investment in infrastructure, which can be expensive. While cloud...
What needs improvement with Apache Spark?
The main concern is the overhead of Java when distributed processing is not necessary. In such cases, operations can often be done on one node, making Spark's distributed mode unnecessary. Conseque...
Which is better, AWS Lambda or Batch?
AWS Lambda is a serverless solution. It doesn’t require any infrastructure, which allows for cost savings. There is no setup process to deal with, as the entire solution is in the cloud. If you use...
What do you like most about AWS Batch?
AWS Batch manages the execution of computing workload, including job scheduling, provisioning, and scaling.
 

Comparisons

 

Also Known As

No data available
Amazon Batch
 

Overview

 

Sample Customers

NASA JPL, UC Berkeley AMPLab, Amazon, eBay, Yahoo!, UC Santa Cruz, TripAdvisor, Taboola, Agile Lab, Art.com, Baidu, Alibaba Taobao, EURECOM, Hitachi Solutions
Hess, Expedia, Kelloggs, Philips, HyperTrack
Find out what your peers are saying about AWS Batch vs. Apache Spark and other solutions. Updated: December 2024.
824,067 professionals have used our research since 2012.