No more typing reviews! Try our Samantha, our new voice AI agent.

Apache Spark vs Spark SQL comparison

Why PeerSpot?
 

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 Hadoop
1st
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
69
Ranking in other categories
Compute Service (6th), Java Frameworks (2nd)
Spark SQL
Ranking in Hadoop
4th
Average Rating
7.8
Reviews Sentiment
7.6
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Hadoop category, the mindshare of Apache Spark is 14.4%, down from 17.1% compared to the previous year. The mindshare of Spark SQL is 5.3%, down from 7.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Hadoop Mindshare Distribution
ProductMindshare (%)
Apache Spark14.4%
Spark SQL5.3%
Other80.3%
Hadoop
 

Featured Reviews

Devindra Weerasooriya - PeerSpot reviewer
Data Architect at Devtech
Provides a consistent framework for building data integration and access solutions with reliable performance
The in-memory computation feature is certainly helpful for my processing tasks. It is helpful because while using structures that could be held in memory rather than stored during the period of computation, I go for the in-memory option, though there are limitations related to holding it in memory that need to be addressed, but I have a preference for in-memory computation. The solution is beneficial in that it provides a base-level long-held understanding of the framework that is not variant day by day, which is very helpful in my prototyping activity as an architect trying to assess Apache Spark, Great Expectations, and Vault-based solutions versus those proposed by clients like TIBCO or Informatica.
Kemal Duman - PeerSpot reviewer
Team Lead, Data Engineering at Nesine.com
Data pipelines have run faster and support flexible batch and streaming transformations
We do not have any performance problems, but we do have some resource problems. Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink. Resource management in Spark SQL should be better. It consumes more resources, which is normal. The main reason we switched from Spark is memory and CPU consumption. The major reason is the resource problem because the number of streaming jobs has been increasing in our company. That is why we considered resource management as a priority. Because of the resource consumption, I would say the development of Spark SQL is better. For development purposes, it is a top product and not difficult to work with, but resources are the major problem. We changed to Flink regardless of development time. Development time is less in Spark compared with Flink.

Quotes from Members

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

Pros

"One of the key features is that Apache Spark is a distributed computing framework. You can help multiple slaves and distribute the workload between them."
"Having everything in the same framework has helped us out a lot."
"Spark Streaming, Spark SQL and MLib in that order."
"The product’s most valuable feature is the SQL tool. It enables us to create a database and publish it."
"I feel the streaming is its best feature."
"The most valuable feature of Apache Spark is its ease of use."
"The most crucial feature for us is the streaming capability. It serves as a fundamental aspect that allows us to exert control over our operations."
"Now, when we're tackling sentiment analysis using NLP technologies, we deal with unstructured data—customer chats, feedback on promotions or demos, and even media like images, audio, and video files. For processing such data, we rely on PySpark. Beneath the surface, Spark functions as a compute engine with in-memory processing capabilities, enhancing performance through features like broadcasting and caching. It's become a crucial tool, widely adopted by 90% of companies for a decade or more."
"I find the Thrift connection valuable."
"One of Spark SQL's most beautiful features is running parallel queries to go through enormous data."
"Spark SQL's efficiency in managing distributed data and its simplicity in expressing complex operations make it an essential part of our data pipeline."
"Overall the solution is excellent."
"The team members don't have to learn a new language and can implement complex tasks very easily using only SQL."
"The speed of getting data, as our TBs are big and it's a lot of data."
"The performance is one of the most important features, and it has an API to process the data in a functional manner."
"The speed of getting data."
 

Cons

"Apache Spark lacks geospatial data."
"There is complexity when it comes to understanding the whole ecosystem, especially for beginners."
"If you have a Spark session in the background, sometimes it's very hard to kill these sessions because of D allocation."
"Apache Spark provides very good performance The tuning phase is still tricky."
"Apache Spark could improve the connectors that it supports."
"I do not know exactly what was the reason to move away from Apache Spark or the underlying database system, but it was simply a decision driven by the customer."
"The migration of data between different versions could be improved."
"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."
"In the next update, we'd like to see better performance for small points of data. It is possible but there are better tools that are faster and cheaper."
"There should be better integration with other solutions."
"In the next release, maybe the visualization of some command-line features could be added."
"Being a new user, I am not able to find out how to partition it correctly. I probably need more information or knowledge. In other database solutions, you can easily optimize all partitions. I haven't found a quicker way to do that in Spark SQL. It would be good if you don't need a partition here, and the system automatically partitions in the best way. They can also provide more educational resources for new users."
"It would be useful if Spark SQL integrated with some data visualization tools."
"This solution could be improved by adding monitoring and integration for the EMR."
"SparkUI could have more advanced versions of the performance and the queries and all."
"The initial setup is a bit complex."
 

Pricing and Cost Advice

"On the cloud model can be expensive as it requires substantial resources for implementation, covering on-premises hardware, memory, and licensing."
"Considering the product version used in my company, I feel that the tool is not costly since the product is available for free."
"Apache Spark is an expensive solution."
"It is an open-source platform. We do not pay for its subscription."
"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."
"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."
"Apache Spark is an open-source tool."
"Apache Spark is an open-source solution, and there is no cost involved in deploying the solution on-premises."
"There is no license or subscription for this solution."
"The on-premise solution is quite expensive in terms of hardware, setting up the cluster, memory, hardware and resources. It depends on the use case, but in our case with a shared cluster which is quite large, it is quite expensive."
"We don't have to pay for licenses with this solution because we are working in a small market, and we rely on open-source because the budgets of projects are very small."
"The solution is bundled with Palantir Foundry at no extra charge."
"The solution is open-sourced and free."
"We use the open-source version, so we do not have direct support from Apache."
report
Use our free recommendation engine to learn which Hadoop solutions are best for your needs.
920,574 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Outsourcing Company
10%
Comms Service Provider
9%
Construction Company
8%
Financial Services Firm
15%
Comms Service Provider
11%
Manufacturing Company
11%
University
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business28
Midsize Enterprise16
Large Enterprise33
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise6
Large Enterprise4
 

Questions from the Community

What is your experience regarding pricing and costs for Apache Spark?
Apache Spark is open-source, so it doesn't incur any charges.
What needs improvement with Apache Spark?
I find that there really lacks the technical depth to do any recommendations for future updates of Apache Spark. I used it for two years for our prototype work and testing things, but because I had...
What is your primary use case for Apache Spark?
I attempted to use Apache Spark in one of our customer projects, but after the initial test, our customer moved to another technology and another database system. I do not have any final remarks on...
What needs improvement with Spark SQL?
We do not have any performance problems, but we do have some resource problems. Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink. Resource manageme...
What is your primary use case for Spark SQL?
Spark SQL has been in our stack for less than one year, though some of our colleagues are using it. It is a useful product for transformation jobs. We generally use Spark SQL for batch processing. ...
What advice do you have for others considering Spark SQL?
Regarding the Catalyst query optimizer, I think we are using it. We were using it in the past, but I am not certain if we use it now. We used it a long time ago. I rate my experience with Spark SQL...
 

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
UC Berkeley AMPLab, Amazon, Alibaba Taobao, Kenshoo, Hitachi Solutions
Find out what your peers are saying about Apache Spark vs. Spark SQL and other solutions. Updated: November 2026.
920,574 professionals have used our research since 2012.