We performed a comparison between Spring Boot 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 solution's framework is stable."
"The most valuable feature of Spring Boot is the microservices and change information. Additionally, there are plenty of features."
"The cloud version is very scalable."
"We like that the product is open-source."
"It's easy to set up the solution."
"Spring Boot's main feature is that it's great for DevOps because you can write your own application. You don't need to install Apache Tomcat. You can create your project easily with a few clicks."
"It's very easy to get started. It's very quick. Most of the configurations are already available. So not much time is spent on setting up things. One can quickly set up and then get rolling."
"The simplicity is excellent."
"The solution is open-source and free to use."
"The solution can scale."
"Dependency Injection is one of the major features which makes our life easier using Spring. It is well documented and has active communities, which provide us enormous help."
"The best feature of Spring MVC is its auto-configuration capabilities."
"The interface is the solution's most valuable aspect."
"Spring MVC is fast and reliable."
"It provides the best documentation for technical support."
"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."
"We have specific algorithms for our Load Balancer or API gateway. So those things, if they could make it more precise, that would be beneficial. Sometimes when we are under pressure or any new person who looks into that stuff, we'll get confused or scared because of some difficulties in understanding Which algorithm needs to be used to implement a Load Balancer. When when we Yeah. Because when we say circuit breaker, we need to use it, and then the user gets a blank circuit breaker. This means we are saying the circuit breaker needs to be moved, and then that circuit breaker needs to be elaborated more. What type of algorithm should I do, and what exactly do I need to get done so that this circuit breaker can help me to resolve my issue? Because, you know, because if you go for the circuit breaker, it will ask to open the new tab, you know, since it will check. If the service is not responding, it will wait and go for another connection. So in similar words, if they can explain it a bit more, that will be helpful. Everyone could do their own Google stuff, and they will get it, but they need help understanding how this could help them to resolve the issue. It will be good if Spring Boot provides information about real-time use cases."
"Spring Boot could improve the interface, error handling, and integration performance."
"It needs to be simplified, more user-friendly."
"Perhaps an even lighter-weight, leaner version could be made available, to compete with alternative solutions, such as NodeJS."
"When the dependencies within those starter packages clash, mismatch or have a hazard, it is hard to solve the issue."
"The solution could improve its flexibility."
"When we change versions, we run into issues."
"If you want to have multiple integrations, the setup phase will become complex."
"I have recently had problems with the changes that were made using Spring Security."
"It can be difficult for a basic user to understand the concepts in this solution, such as inversion of control."
"It could provide faster performance."
"We would like the deployment of this solution to be easier as, at present, it is quite complicated."
"The documentation for Spring MVC could improve."
"I saw some error messages coming up when they were getting problems actually viewing all the reports."
"Spring MVC could improve the integration with DevOps and other applications."
"The initial setup could be more straightforward."
Spring Boot is ranked 1st in Java Frameworks with 38 reviews while Spring MVC is ranked 3rd in Java Frameworks with 16 reviews. Spring Boot is rated 8.4, while Spring MVC is rated 8.4. The top reviewer of Spring Boot writes "It's highly scalable, secure, and provides all the enhanced tools I need. ". On the other hand, the top reviewer of Spring MVC writes "Straightforward setup, highly stable, and useful online support". Spring Boot is most compared with Jakarta EE, Open Liberty, Apache Spark, Eclipse MicroProfile and Helidon, whereas Spring MVC is most compared with Jakarta EE, Apache Spark, Open Liberty, Oracle Application Development Framework and Vert.x. See our Spring Boot 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.
