AWS Lambda vs Apache Spark comparison

Cancel
You must select at least 2 products to compare!
Apache Logo
2,893 views|2,256 comparisons
89% willing to recommend
Amazon Web Services (AWS) Logo
11,937 views|8,175 comparisons
94% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Apache Spark and AWS Lambda based on real PeerSpot user reviews.

Find out in this report how the two Compute Service solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed AWS Lambda vs. Apache Spark Report (Updated: May 2024).
772,649 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"Spark can handle small to huge data and is suitable for any size of company.""Apache Spark provides a very high-quality implementation of distributed data processing.""With Spark, we parallelize our operations, efficiently accessing both historical and real-time data.""The memory processing engine is the solution's most valuable aspect. It processes everything extremely fast, and it's in the cluster itself. It acts as a memory engine and is very effective in processing data correctly.""The processing time is very much improved over the data warehouse solution that we were using.""The most valuable feature is the Fault Tolerance and easy binding with other processes like Machine Learning, graph analytics.""ETL and streaming capabilities.""There's a lot of functionality."

More Apache Spark Pros →

"The stability is good.""Technical support has been great in general.""You can spin up anything instantly without any investment.""The installation and configuration of the solution is straightforward.""AWS Lambda's best features are log analysis and event triggering and actioning.""We have no issues with the technical support.""The support from AWS Lambda is very good, they are responsive.""Amazon takes care of the scalability. That's the right way. It's automatic and it's fully managed. That's one benefit of Lambda."

More AWS Lambda Pros →

Cons
"Spark could be improved by adding support for other open-source storage layers than Delta Lake.""Needs to provide an internal schedule to schedule spark jobs with monitoring capability.""Apache Spark provides very good performance The tuning phase is still tricky.""They could improve the issues related to programming language for the platform.""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.""We are building our own queries on Spark, and it can be improved in terms of query handling.""Apache Spark can improve the use case scenarios from the website. There is not any information on how you can use the solution across the relational databases toward multiple databases.""The initial setup was not easy."

More Apache Spark Cons →

"AWS Lambda has some size limitations in the code line, you can't do a couple of functions to do the job.""My opinion is that the integration could be improved in this solution. We have had some difficulties integrating the EC2 module, but we found a solution for that by ourselves.""AWS Lambda's GUI could be improved with a twist or tweak in its look and feel to make it more impressive.""The tool changes its UI every month which is very frustrating for me. I don’t know why AWS keeps changing the UI. They can’t stick to a specific one""Amazon doesn't have enough local support based in our country.""AWS Lambda should support additional languages.""If you're running a new application with a significant load, you need to be prepared for potential bottlenecks.""Lambda could be improved in the sense that some of the things done with Lambda function take some time. So the performance could be better and faster."

More AWS Lambda Cons →

Pricing and Cost Advice
  • "Since we are using the Apache Spark version, not the data bricks version, it is an Apache license version, the support and resolution of the bug are actually late or delayed. The Apache license is free."
  • "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."
  • "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 expensive solution."
  • "Spark is an open-source solution, so there are no licensing costs."
  • "On the cloud model can be expensive as it requires substantial resources for implementation, covering on-premises hardware, memory, and licensing."
  • "It is an open-source solution, it is free of charge."
  • More Apache Spark Pricing and Cost Advice →

  • "AWS is slightly more expensive than Azure."
  • "Its pricing is on the higher side."
  • "The price of the solution is reasonable and it is a pay-per-use model. It is very good for cost optimization."
  • "The cost is based on runtime."
  • "The fees are volume-based."
  • "AWS Lambda is inexpensive."
  • "Lambda is a good and cheap solution and I would recommend it to those without a huge payload."
  • "For licensing, we pay a yearly subscription."
  • More AWS Lambda Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Compute Service solutions are best for your needs.
    772,649 professionals have used our research since 2012.
    Questions from the Community
    Top Answer:We use Spark to process data from different data sources.
    Top Answer:In data analysis, you need to take real-time data from different data sources. You need to process this in a subsecond, and do the transformation in a subsecond
    Top Answer: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… more »
    Top Answer:The tool scales automatically based on the number of incoming requests.
    Top Answer:We only need to pay for the compute time our code consumes. The solution does not cost much.
    Ranking
    5th
    out of 16 in Compute Service
    Views
    2,893
    Comparisons
    2,256
    Reviews
    26
    Average Words per Review
    444
    Rating
    8.7
    1st
    out of 16 in Compute Service
    Views
    11,937
    Comparisons
    8,175
    Reviews
    39
    Average Words per Review
    391
    Rating
    8.6
    Comparisons
    Spring Boot logo
    Compared 31% of the time.
    AWS Batch logo
    Compared 10% of the time.
    Spark SQL logo
    Compared 9% of the time.
    SAP HANA logo
    Compared 8% of the time.
    Apache NiFi logo
    Compared 4% of the time.
    AWS Batch logo
    Compared 27% of the time.
    Apache NiFi logo
    Compared 16% of the time.
    AWS Fargate logo
    Compared 7% of the time.
    Google Cloud Dataflow logo
    Compared 6% of the time.
    Learn More
    Overview

    Spark provides programmers with an application programming interface centered on a data structure called the resilient distributed dataset (RDD), a read-only multiset of data items distributed over a cluster of machines, that is maintained in a fault-tolerant way. It was developed in response to limitations in the MapReduce cluster computing paradigm, which forces a particular linear dataflowstructure on distributed programs: MapReduce programs read input data from disk, map a function across the data, reduce the results of the map, and store reduction results on disk. Spark's RDDs function as a working set for distributed programs that offers a (deliberately) restricted form of distributed shared memory

    AWS Lambda is a compute service that lets you run code without provisioning or managing servers. AWS Lambda executes your code only when needed and scales automatically, from a few requests per day to thousands per second. You pay only for the compute time you consume - there is no charge when your code is not running. With AWS Lambda, you can run code for virtually any type of application or backend service - all with zero administration. AWS Lambda runs your code on a high-availability compute infrastructure and performs all of the administration of the compute resources, including server and operating system maintenance, capacity provisioning and automatic scaling, code monitoring and logging. All you need to do is supply your code in one of the languages that AWS Lambda supports (currently Node.js, Java, C# and Python).

    You can use AWS Lambda to run your code in response to events, such as changes to data in an Amazon S3 bucket or an Amazon DynamoDB table; to run your code in response to HTTP requests using Amazon API Gateway; or invoke your code using API calls made using AWS SDKs. With these capabilities, you can use Lambda to easily build data processing triggers for AWS services like Amazon S3 and Amazon DynamoDB process streaming data stored in Amazon Kinesis, or create your own back end that operates at AWS scale, performance, and security.

    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
    Netflix
    Top Industries
    REVIEWERS
    Computer Software Company33%
    Financial Services Firm12%
    University9%
    Marketing Services Firm6%
    VISITORS READING REVIEWS
    Financial Services Firm25%
    Computer Software Company13%
    Manufacturing Company7%
    Comms Service Provider5%
    REVIEWERS
    Financial Services Firm24%
    Computer Software Company21%
    Government5%
    Comms Service Provider5%
    VISITORS READING REVIEWS
    Educational Organization48%
    Financial Services Firm12%
    Computer Software Company8%
    Manufacturing Company4%
    Company Size
    REVIEWERS
    Small Business42%
    Midsize Enterprise16%
    Large Enterprise42%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise12%
    Large Enterprise71%
    REVIEWERS
    Small Business38%
    Midsize Enterprise15%
    Large Enterprise47%
    VISITORS READING REVIEWS
    Small Business10%
    Midsize Enterprise52%
    Large Enterprise38%
    Buyer's Guide
    AWS Lambda vs. Apache Spark
    May 2024
    Find out what your peers are saying about AWS Lambda vs. Apache Spark and other solutions. Updated: May 2024.
    772,649 professionals have used our research since 2012.

    Apache Spark is ranked 5th in Compute Service with 60 reviews while AWS Lambda is ranked 1st in Compute Service with 70 reviews. Apache Spark is rated 8.4, while AWS Lambda is rated 8.6. The top reviewer of Apache Spark writes "Reliable, able to expand, and handle large amounts of data well". On the other hand, the top reviewer of AWS Lambda writes "An easily scalable solution with a variety of use cases and valuable event-based triggers". Apache Spark is most compared with Spring Boot, AWS Batch, Spark SQL, SAP HANA and Apache NiFi, whereas AWS Lambda is most compared with AWS Batch, Amazon EC2 Auto Scaling, Apache NiFi, AWS Fargate and Google Cloud Dataflow. See our AWS Lambda vs. Apache Spark report.

    See our list of best Compute Service vendors.

    We monitor all Compute Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.