We performed a comparison between Jakarta EE and Spring MVC based on real PeerSpot user reviews.
Find out in this report how the two Java Frameworks solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The feature that allows a variation of work space based on the application being used."
"Configuring, monitoring, and ensuring observability is a straightforward process."
"Jakarta EE's best features include REST services, configuration, and persistent facilities. It's also incredibly cloud friendly."
"The best feature of Spring MVC is its auto-configuration capabilities."
"The solution can scale."
"The interface is the solution's most valuable aspect."
"The most valuable feature is simplicity."
"It provides the best documentation for technical support."
"The most valuable feature of Spring MVC is the configuration, such as WAF."
"The solution is open-source and free to use."
"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."
"All the customization and plugins can make the interface too slow and heavy in some situations."
"It would be great if we could have a UI-based approach or easily include the specific dependencies we need."
"Jakarta EE's configuration could be simpler, which would make it more useful as a developer experience."
"We would like the deployment of this solution to be easier as, at present, it is quite complicated."
"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."
"I have recently had problems with the changes that were made using Spring Security."
"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."
"It can be difficult for a basic user to understand the concepts in this solution, such as inversion of control."
"Spring MVC could improve the integration with DevOps and other applications."
"The solution could be simplified quite a bit. It's unnecessarily complicated in some areas."
"Spring IDE needs some work and improvement. We have faced many issues when adding third-party Eclipse plugins."
Jakarta EE is ranked 4th in Java Frameworks with 3 reviews while Spring MVC is ranked 3rd in Java Frameworks with 16 reviews. Jakarta EE is rated 7.4, while Spring MVC is rated 8.4. The top reviewer of Jakarta EE writes "A robust enterprise Java capabilities with complex configuration involved, making it a powerful choice for scalable applications while requiring a learning curve". On the other hand, the top reviewer of Spring MVC writes "Straightforward setup, highly stable, and useful online support". Jakarta EE is most compared with Spring Boot, Amazon Corretto, Eclipse MicroProfile, Vert.x and Apache Spark, whereas Spring MVC is most compared with Spring Boot, Apache Spark, Open Liberty, Oracle Application Development Framework and Vert.x. See our Jakarta EE vs. Spring MVC report.
See our list of best Java Frameworks vendors.
We monitor all Java Frameworks 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.