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

Jakarta EE vs Spring MVC 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

Jakarta EE
Ranking in Java Frameworks
3rd
Average Rating
7.4
Number of Reviews
3
Ranking in other categories
No ranking in other categories
Spring MVC
Ranking in Java Frameworks
7th
Average Rating
8.4
Reviews Sentiment
5.9
Number of Reviews
15
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2026, in the Java Frameworks category, the mindshare of Jakarta EE is 16.8%, down from 23.7% compared to the previous year. The mindshare of Spring MVC is 4.9%, up from 3.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Java Frameworks Market Share Distribution
ProductMarket Share (%)
Jakarta EE16.8%
Spring MVC4.9%
Other78.3%
Java Frameworks
 

Featured Reviews

Mortaza Ghahramani - PeerSpot reviewer
Senior Java Software Engineer at eDreams ODIGEO
Cloud-friendly but has problems with configuration
I primarily use Jakarta EE as a business enterprise product Jakarta EE's best features include REST services, configuration, and persistent facilities. It's also incredibly cloud friendly. Jakarta EE's configuration could be simpler, which would make it more useful as a developer experience.…
reviewer2151066 - PeerSpot reviewer
Software Engineer at a financial services firm with 10,001+ employees
Straightforward setup, highly stable, and useful online support
We are using Spring MVC based on our business problem statements One of the most valuble features for our business is the bootstrap which allows our developers to save time when developing code. Additionally, it has a built-in library that is useful. The most valuable features of Spring MVC are…

Quotes from Members

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

Pros

"Configuring, monitoring, and ensuring observability is a straightforward process."
"The feature that allows a variation of work space based on the application being used."
"Jakarta EE's best features include REST services, configuration, and persistent facilities. It's also incredibly cloud friendly."
"The most valuable feature is simplicity."
"The interface is the solution's most valuable aspect."
"Spring has a speedy development process with a lightweight framework."
"The solution is open-source and free to use."
"The best feature of Spring MVC is its auto-configuration capabilities."
"We have found Spring is easy to use and learn."
"When we shifted from our legacy frameworks to the Spring framework, we discovered that Spring definitely made our development easier. One good example is that there is a lot of boiler plate code available that you don't have to write from scratch, making the development of web applications a much simpler process."
"The most valuable feature of Spring MVC is the configuration, such as WAF."
 

Cons

"All the customization and plugins can make the interface too slow and heavy in some situations."
"Jakarta EE's configuration could be simpler, which would make it more useful as a developer experience."
"It would be great if we could have a UI-based approach or easily include the specific dependencies we need."
"Spring MVC could improve the integration with DevOps and other applications."
"Spring IDE​ needs some work and improvement. We have faced many issues when adding third-party Eclipse plugins."
"I saw some error messages coming up when they were getting problems actually viewing all the reports."
"The documentation for Spring MVC could improve."
"The newer versions of Spring MVC have released a lot of features that we are not using right now because, in many cases, we are limited to running older versions. As such, it would be nice if Spring were to improve support for upgrading to newer versions, especially for legacy applications."
"It could provide faster performance."
"It can be difficult for a basic user to understand the concepts in this solution, such as inversion of control."
"Adding more modules takes about 10 to 15 minutes each. It would be nice if they could reduce that part. The deployment time is a little high."
 

Pricing and Cost Advice

"I would rate Jakarta EE's pricing seven out of ten."
"It is an open-source solution."
"We are using the open-source version of the solution."
"This is an open-source solution, so there are no license costs involved with using it."
"The solution is free."
"Spring MVC is open source and free."
report
Use our free recommendation engine to learn which Java Frameworks solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
12%
Comms Service Provider
10%
University
9%
Financial Services Firm
18%
Computer Software Company
15%
Comms Service Provider
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise2
Large Enterprise11
 

Questions from the Community

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...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

No data available
Spring by Pivotal, Spring, Spring Framework
 

Overview

 

Sample Customers

Information Not Available
EMC, Aridhia, CoreLogic, CenturyLink, Humana, Purdue University, Tampon Run, ArtsPool, Charity Water, Center for ReSource Conservation, Manos Teatrales
Find out what your peers are saying about Jakarta EE vs. Spring MVC and other solutions. Updated: December 2025.
881,082 professionals have used our research since 2012.