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

AWS Fargate vs Apache Spark comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

Categories and Ranking

Apache Spark
Ranking in Compute Service
4th
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
65
Ranking in other categories
Hadoop (1st), Java Frameworks (2nd)
AWS Fargate
Ranking in Compute Service
2nd
Average Rating
8.6
Reviews Sentiment
7.5
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Compute Service category, the mindshare of Apache Spark is 11.2%, up from 9.7% compared to the previous year. The mindshare of AWS Fargate is 14.7%, down from 17.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Compute Service
 

Featured Reviews

Ilya Afanasyev - PeerSpot reviewer
Reliable, able to expand, and handle large amounts of data well
We use batch processing. It works well with our formats and file versions. There's a lot of functionality. In our pipeline each hour, we make a copy of data from MongoDB, of the changes from MongoDB to some specific file. Each time pipeline copied all of the data, it would do it each time without changes to all of the tables. Tables have a lot of data, and in the last MongoDB version, there is a possibility to read only changed data. This reduced the cost and configuration of the cluster, and we saved about $150,000. The solution is scalable. It's a stable product.
Subrata Mukherjee - PeerSpot reviewer
Boost demand response with cost-efficient serverless architecture
We are a venture builder company, and if we select AWS for our product. Our design is based on a serverless architecture model. ECS Fargate is the most convenient way in terms of scalability, integration, and cost control Thanks to the serverless model and easy integration features, a few…

Quotes from Members

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

Pros

"The processing time is very much improved over the data warehouse solution that we were using."
"It is highly scalable, allowing you to efficiently work with extensive datasets that might be problematic to handle using traditional tools that are memory-constrained."
"The main feature that we find valuable is that it is very fast."
"The product's deployment phase is easy."
"The scalability has been the most valuable aspect of the solution."
"Spark is used for transformations from large volumes of data, and it is usefully distributed."
"The product’s most valuable feature is the SQL tool. It enables us to create a database and publish it."
"Apache Spark can do large volume interactive data analysis."
"It allows for focusing on applications instead of managing infrastructure."
"By using a server's compute resources, one can observe the resource metrics. With AWS, one can determine when servers will be used based on CloudWatch results. For example, CloudWatch informs the application and service platform when the hit ratio has reached the threshold value."
"I like their containerization service. You can use Docker or something similar and deploy quickly without the know-how related to, for example, Kubernetes. If you use AKS or Kubernetes, then you have to have the know-how. But for Fargate, you don't need to have the know-how there. You just deploy the container or the image, and then you have the container, and you can use it as AWS takes care of the rest. This makes it easier for those getting started or if you don't have a strong DevOps team inside your organization."
"AWS Fargate has many valuable services. It does the job with minimal trouble. It's very observable. You can see what's going on and you have logs. You have everything. You can troubleshoot it. It's affordable and it's flexible."
"Fargate's integration with other AWS services is really good."
"The most valuable feature of Fargate is that it's self-managed. You don't have to configure your own clusters or deploy any Kubernetes clusters. This simplifies the initial deployment and scaling process."
"AWS Fargate automatically scales to meet demand, making it ideal for applications with variable workloads."
"Fargate itself is a stable product. We are quite satisfied with its performance."
 

Cons

"It would be beneficial to enhance Spark's capabilities by incorporating models that utilize features not traditionally present in its framework."
"The logging for the observability platform could be better."
"It requires overcoming a significant learning curve due to its robust and feature-rich nature."
"There could be enhancements in optimization techniques, as there are some limitations in this area that could be addressed to further refine Spark's performance."
"Its UI can be better. Maintaining the history server is a little cumbersome, and it should be improved. I had issues while looking at the historical tags, which sometimes created problems. You have to separately create a history server and run it. Such things can be made easier. Instead of separately installing the history server, it can be made a part of the whole setup so that whenever you set it up, it becomes available."
"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."
"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."
"From my perspective, the only thing that needs improvement is the interface, as it was not easily understandable."
"There is a tool named Compose that helps in converting the Docker Compose file into a Kubernetes file. For ECS and Fargate, AWS reads a Dockerfile and helps with conversion. However, I am uncertain if it's ready for deployment after conversion."
"I heard from my team that it's not easy to predict the cost. That is the only issue we have with AWS Fargate, but I think that's acceptable. AWS Fargate isn't user-friendly. Anything related to Software as a Service or microservice architecture is not easy to implement. You're required to have DevOps from your side to implement the solution. AWS Fargate is just a temporary solution for us. When we grow to a certain level, we may use AKS for better control."
"The main area for improvement is the cost, which could be lowered to be more competitive with other major cloud providers."
"Sometimes, Fargate can be really hard to configure."
"I would like to see enhanced faster application scaling and better integration with the elastic file system to unify storage volumes and improve the launch time of instances."
"I would like to see the older dashboard instead of the newer version. I don't like the new dashboard."
"If there are any options to manage containers, that would be good. That relates more to the cost point. For example, over the next three months, I'll be making a comparison between solutions like CAST AI and other software-as-a-service platforms that offer Kubernetes management with an emphasis on cost reduction."
"Challenges include higher costs for smaller clients, limited control over underlying infrastructure customization, and potential latencies during task startup."
 

Pricing and Cost Advice

"Apache Spark is open-source. You have to pay only when you use any bundled product, such as Cloudera."
"We are using the free version of the solution."
"Licensing costs can vary. For instance, when purchasing a virtual machine, you're asked if you want to take advantage of the hybrid benefit or if you prefer the license costs to be included upfront by the cloud service provider, such as Azure. If you choose the hybrid benefit, it indicates you already possess a license for the operating system and wish to avoid additional charges for that specific VM in Azure. This approach allows for a reduction in licensing costs, charging only for the service and associated resources."
"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."
"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."
"Considering the product version used in my company, I feel that the tool is not costly since the product is available for free."
"It is quite expensive. In fact, it accounts for almost 50% of the cost of our entire project."
"On the cloud model can be expensive as it requires substantial resources for implementation, covering on-premises hardware, memory, and licensing."
"I rate the price of AWS Fargate a four out of five."
"We would advise that this solution has a slightly-higher price point than others on the market. There is a free plan available for start-ups, but the free and lower range licensing models do not provide the full functionality."
report
Use our free recommendation engine to learn which Compute Service solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Computer Software Company
13%
Manufacturing Company
8%
Comms Service Provider
5%
Financial Services Firm
24%
Computer Software Company
13%
Government
8%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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 Spark solution could improve in scheduling tasks and managing dependencies. Spark alone cannot handle sequential tasks, requiring environments like Airflow scheduler or scripts. For instance, o...
What do you like most about AWS Fargate?
The most valuable feature of Fargate is that it's self-managed. You don't have to configure your own clusters or deploy any Kubernetes clusters. This simplifies the initial deployment and scaling p...
What needs improvement with AWS Fargate?
The monitoring capabilities of AWS Fargate could be improved and made more robust. The error handling aspect sometimes causes issues and can get stuck during deployment, making the process not very...
What advice do you have for others considering AWS Fargate?
I would recommend AWS Fargate as an alternative to AWS Lambda for running loads or hosting a service. It is a good service for keeping instances running, which minimizes initial latency. Overall, I...
 

Comparisons

 

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
Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Find out what your peers are saying about AWS Fargate vs. Apache Spark and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.