Spring MVC Overview

Spring MVC is the #5 ranked solution in our list of top Java Frameworks. It is most often compared to Jakarta EE: Spring MVC vs Jakarta EE

What is Spring MVC?

Spring MVC is a Java web framework built on the Servlet API and has been included in the Spring Framework from the very beginning.  It handles web applications that use server-rendered HTML user interface, REST APIs, and much more.  The documentation includes Spring MVCView TechnologiesCORS Support, and WebSocket Support

For baseline information and compatibility with Servlet container and Java EE version ranges please visit the Spring Framework Wiki.

Spring MVC is also known as Spring by Pivotal, Spring, Spring Framework.

Spring MVC Customers

EMC, Aridhia, CoreLogic, CenturyLink, Humana, Purdue University, Tampon Run, ArtsPool, Charity Water, Center for ReSource Conservation, Manos Teatrales

Spring MVC Video

Filter Archived Reviews (More than two years old)

Filter by:
Filter Reviews
Filter Unavailable
Company Size
Filter Unavailable
Job Level
Filter Unavailable
Filter Unavailable
Filter Unavailable
Order by:
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Showingreviews based on the current filters. Reset all filters
Department Manager at a tech services company with 51-200 employees
Real User
Employs a speedy development process with a lightweight framework

What is our primary use case?

Spring is used as a J2EE framework for our Java applications server side. We are using MVC, Hibernate, and Security.

How has it helped my organization?

Spring has a speedy development process with a lightweight framework. We have found Spring is easy to use and learn. 

What is most valuable?

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.

What needs improvement?

Spring IDE needs some work and improvement. We have faced many issues when adding third-party Eclipse plugins.

For how long have I used the solution?

One to three years.
Principal Architect at a tech services company with 11-50 employees
Real User
The product has been scaled to hundreds of simultaneous users, without issue.

What is our primary use case?

Mostly REST service and web application development on RDBMS products

What other advice do I have?

Finalize how you wish to configure the business tier and where you wish to place data access and transaction logic first. Use established solution patterns. Decide up-front where you wish to apply Filters and how you wish to handle HTTP sessions.