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

Apache Spark vs Spring Boot comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 12, 2025

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 Java Frameworks
2nd
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
64
Ranking in other categories
Hadoop (1st), Compute Service (4th)
Spring Boot
Ranking in Java Frameworks
1st
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
38
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Java Frameworks category, the mindshare of Apache Spark is 6.7%, down from 7.7% compared to the previous year. The mindshare of Spring Boot is 42.0%, down from 43.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Java Frameworks
 

Q&A Highlights

MT
Aug 28, 2023
 

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.
RajuGottupalli - PeerSpot reviewer
Minimizes a lot of coding, improves the time to market, and is easily deployable and configurable
Spring Boot is a bounded framework. The services we develop are purely synchronous services, so there's a blocking and waiting state. This is a big problem in microservices. To avoid this problem, we have to make the service a reactive session. It has to be reactive to a particular load, particular condition, or based on the number of requests hitting the particular service. All these factors make the service a reactor. There's another module in which Spring Boot provides spring reflex. This module enables the reactiveness of the service, meaning that it eliminates the blocking and waiting state. For example, if you're sending a get operation or a post operation, there won't be any waiting for it to actually hit that particular network to get the data from another service. It continuously flows the request, and there is a zero waiting pack. Vert.x is another good framework where there are similar features or similar benefits with having a reactive session. Spring Boot is a license resource, so it's a framework where we can customize our solution or a particular requirement to build a good solution using Spring Boot. But it's an opinionated framework, meaning that it's completely bounded. You have only one direction to find a solution, whereas Vert.x is an unopinionated framework. Unopinionated is a kind of a toolkit where you can have more optimization and a more flexible solution, which is suitable to your requirements. In Spring Boot, the opportunities are limited. With Vert.x and other programming tools, we have multiple options to explore the solution in a different way and achieve a nonfunctional requirement of thousands transactions in a second. Spring Boot might not support this kind of non-functional requirement. Vert.X is a very good solution to solve critical NFRs for a particular application.

Quotes from Members

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

Pros

"I appreciate everything about the solution, not just one or two specific features. The solution is highly stable. I rate it a perfect ten. The solution is highly scalable. I rate it a perfect ten. The initial setup was straightforward. I recommend using the solution. Overall, I rate the solution a perfect ten."
"Spark can handle small to huge data and is suitable for any size of company."
"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."
"The processing time is very much improved over the data warehouse solution that we were using."
"The product's initial setup phase was easy."
"There's a lot of functionality."
"The distribution of tasks, like the seamless map-reduce functionality, is quite impressive."
"The main feature that we find valuable is that it is very fast."
"The API gateway and cloud configuration allows us to configure the properties outside of the service with respect to enrollment."
"Spring Boot's most valuable functionalities include inversion of control, dependency injection, and the ability to gather all services, models, and controllers together for easy connectivity to your REST API, as well as the ability to build a modular response and request system. It seamlessly integrates with various backends, such as SQL, events, and messaging systems, making it a user-friendly and efficient Java tool. Additionally, it functions as a reliable business transaction layer, providing excellent support for front-end and back-end visual tools."
"Spring Boot is much easier when it comes to the configuration, setup, installation, and deployment of your applications, compared to any kind of MVC framework. It has everything within a single framework."
"The solution's framework is stable."
"Spring Boot facilitates the use of Java which is open source. We use Github and other libraries that are available which assist in the building we need to do."
"The cloud version is very scalable."
"This solution is really user friendly. In terms of prototyping, it's really fast to build the applications we want to test to complete a proof of concept."
"It gives you confidence in a readily available platform."
 

Cons

"The solution’s integration with other platforms should be improved."
"When using Spark, users may need to write their own parallelization logic, which requires additional effort and expertise."
"We've had problems using a Python process to try to access something in a large volume of data. It crashes if somebody gives me the wrong code because it cannot handle a large volume of data."
"Apache Spark lacks geospatial data."
"The setup I worked on was really complex."
"When you first start using this solution, it is common to run into memory errors when you are dealing with large amounts of data."
"In data analysis, you need to take real-time data from different data sources. You need to process this in a subsecond, do the transformation in a subsecond, and all that."
"From my perspective, the only thing that needs improvement is the interface, as it was not easily understandable."
"The cross framework compatibility has some shortcomings. With JUnit Test Runner and Spring Boot, it's really tedious to make them both work to write the test cases."
"This is a really good solution for me and I can't think of anything that can be improved."
"The services we develop are purely synchronous services, so there's a blocking and waiting state. This is a big problem in microservices."
"We'd like them to develop more supporting testing."
"The tool's documentation could be improved, especially by tying it back to frequently asked questions and issues users have. A feedback loop in which the documentation targets the most commonly asked user questions would make using the solution easier. Essentially, I want a more user-centered approach to documentation rather than a purely technical focus."
"Spring Boot could improve the interface, error handling, and integration performance."
"If you want to have multiple integrations, the setup phase will become complex."
"Spring Boot can improve the dependency tree that we use for libraries. It would be helpful if it was less complex."
 

Pricing and Cost Advice

"We are using the free version of the solution."
"Considering the product version used in my company, I feel that the tool is not costly since the product is available for free."
"On the cloud model can be expensive as it requires substantial resources for implementation, covering on-premises hardware, memory, and licensing."
"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."
"Apache Spark is an expensive solution."
"Apache Spark is an open-source tool."
"It is an open-source platform. We do not pay for its subscription."
"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."
"As Spring Boot is an open-source tool, it's free."
"It's an open-source solution."
"If you want support there is paid enterprise version with support available."
"Spring Boot is open source."
"It's open-source software, so it's free. It's a community license."
"Spring Boot is open source. It's a free tool and free framework."
"Spring Boot is an open source solution, it is free to use."
"This is an open-source product."
report
Use our free recommendation engine to learn which Java Frameworks solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
27%
Computer Software Company
13%
Manufacturing Company
7%
University
5%
Financial Services Firm
26%
Computer Software Company
14%
Government
7%
Manufacturing Company
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 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...
What do you like most about Spring Boot?
1. Open Source2. Excellent Community Support -- Widely used across different projects -- so your search for answers would be easy and almost certain.3. Extendable Stack with a wide array of availab...
Which is better - Spring Boot or Eclipse MicroProfile?
Springboot is a Java-based solution that is very popular and easy to use. You can use it to build applications quickly and confidently. Springboot has a very large, helpful learning community, whic...
Which is better - Spring Boot or Jakarta EE?
Our organization ran comparison tests to determine whether the Spring Boot or Jakarta EE application creation software was the better fit for us. We decided to go with Spring Boot. Spring Boot offe...
 

Comparisons

 

Learn More

 

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
Information Not Available
Find out what your peers are saying about Apache Spark vs. Spring Boot and other solutions. Updated: January 2025.
831,265 professionals have used our research since 2012.