Spring MVC Reviews

In my organization, I belong to the software development department as part of the Java application team (comprising 20-25 people) and we use various tools related to Java development, including Spring MVC, in our work. Our primary use of Spring involves the development of web applications which are accessed through a browser.

The Spring framework has many modules that we use for our in-house development and each of them are integrated with each other. For example, we use Spring Hibernate integration as well as Spring JPA, among others. It's not a one-size-fits-all solution that Spring provides in the sense that we have to use several additional modules under the Spring umbrella.

We are not currently using the latest version of Spring even for newer applications due to the limitations imposed by the various platforms that we run. Some versions of Spring are only supported by certain versions of Java, and we also have legacy applications which require the use of older versions.

As for our infrastructure, everything is private and we are not on the cloud right now.

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 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.

We have been using Spring MVC for almost ten years.

It's a very stable solution. 

It's highly scalable.

Spring has excellent community support, not least because it's an open source framework. Its community is very vibrant and the software is used by a large number of developers. So for almost all the issues you might encounter, it's easy to find a solution on the Internet.

As compared to other frameworks, Spring is a moderate level framework and the deployment is not dependent on Spring itself, but rather it is dependent on the platform that you are using.

The main factors for setting up Spring MVC are how we go about packaging our application and where we intend to deploy it. By itself, Spring MVC is not part of the deployment process for our applications. It's a development framework and not a deployment framework, and so the deployment depends on which platform we use. Currently, we are using the Oracle WebLogic platform for deployment, and our deployment model is a very formal process. For local development and deployment, we deploy it ourselves in-house, but for deployments on staging or production servers, it is done by a different team and they take their own time and use their own methods to deploy Spring. 

Spring MVC is open source and free. 

Speaking from our own experience, Spring MVC has been one of the easiest frameworks to adopt. This is largely because Spring is based on the same MVC pattern as our legacy approaches to web application development and it has been a natural progression for us.

Before adopting anything, you first need to know your requirements and then you need to read up about it (e.g. check the Internet). The same applies with Spring MVC. You should only adopt it if it suits your requirements. However, if you do decide to go with Spring, I can assure you that you won't regret it. It's a very good framework. 

I would rate Spring MVC a nine out of ten.

I use Spring MVC for applications on the web.

The most valuable feature of Spring MVC is the configuration, such as WAF.

Spring MVC could improve the integration with DevOps and other applications.

I have been using Spring MVC for six years.

Spring MVC is scalable.

We have approximately 100 people using this solution in my company.

The initial setup of Spring MVC was not very difficult. The process took approximately 10 minutes.

I rate Spring MVC an eight out of ten.

The solution is deployed depending on your architect and what you want to do. If you want to have your solution on-premises, it's no problem, but it's cloud-ready.

I am using the latest version.

It's very light and well designed. If you deep dive into the way this framework is designed, it is very good. If you make a comparison, with Java EE, which was the first way to develop an enterprise application in Java, you have to use an application server. They're huge in terms of infrastructure. We containerize everything in order to use orchestration with CI/CD and so on.

Spring gives you the opportunity to develop architecture in the simplest way possible. It comes with everything you would want in terms of security. If you want to access the database, you have the ability to do that. If you want to make micro-service architecture, it is very simple, and you can integrate the API Gateway. You can use it to integrate services discovery.

There are many features that you can use very easily. There is also a very good community, so you can rapidly get a solution to any of your problems.

It can be difficult for a basic user to understand the concepts in this solution, such as inversion of control. There are so many concepts that you have to understand before mastering this framework.

I have been using this solution for more than eight years.

It's very stable.

In terms of support, there is a good community behind Spring. It's not difficult to find support in groups to find an answer to your question.

The solution is free.

I would rate this solution 8 out of 10.

The solution is primarily used for web services such as monolithic applications, like C applications which have already been running for a very long time.

The solution is stable and reliable. 

Developing web applications are quite easy there.

The solution is open-source and free to use.

The scalability is limited. 

The initial setup could be more straightforward. 

I've been using the solution for five years. 

We have a bit of a problem with scalability. That's why when we moved to MicroSys Architecture - it adds more value.

At this point, every few people are actually using the solution in our organization at this point. I'm not sure if there are any real plans to increase usage at this point in time. 

I've never contacted technical support. Therefore, I cannot rate how helpful their services are. 

We did not use different Java Frameworks before MVC.

The initial setup could be more straightforward. It's not very easy to accomplish a deployment. It took a very long time to deploy everything.

Spring is actually open-source. Only whatever the new Java versions coming out which are higher than Java 11 would need premium support, which costs money.

I'm not sure which version of the solution I'm using. 

I would not recommend MVC. Rather, I would recommend the use of Spring Boot as Spring Boot also supports all the web services and has even more additional features. That, and it is easy to use.

I'd rate MVC at a six out of ten.

We use the solution for the development of our web applications.

The solution could provide faster performance. Also, its framework must be more accessible. In addition, its native image support needs improvement.

I rate the solution's stability an eight or nine.

I rate the solution's scalability an eight out of ten. It depends on the way you develop the application.

The solution provides the best documentation for technical support. Also, we refer to online portals in case of queries.

Positive

I rate the solution's initial setup process a seven out of ten. My team includes around 30 to 40 executives, including managers, developers, and consultants involved in the deployment. It takes about two years to complete.

It is an open-source solution.

The solution is user-friendly and provides good documentation as well. I rate it an eight out of ten.

We're primarily using the solution to develop the content, web pages, and data system. We then suggest our system to our customers.

The interface is the solution's most valuable aspect.

The solution is very helpful in developing front pages.

The initial setup is simple.

The scalability and stability are pretty good.

It is a little bit complicated and heavy. It should be more simple and light.

I've been dealing with the solution for two years at this point. It hasn't been too long.

The stability has been good over the past few years. We don't have any complaints. It doesn't crash or freeze. I can't recall experience bugs. It's reliable.

We haven't had any issues when it comes to scalability. It's pretty good. There aren't really any limitations.

We've never had to contact technical support, so I can't speak to how knowledgable or responsive they are.

I only really have experience with Spring. I haven't used other solutions. I'm not sure what others would offer, and if it's more or less. For our purposes, Spring seems to work well.

The initial setup was not complex. It was pretty straightforward. I'd describe the process as rather easy.

The cost is quite high. We're using AWS cloud and we find that it's very expensive on it. We're actually looking to see if we can find a solution that's not as expensive as AWS.

We're just customers. We don't have a special relationship with the company.

Overall, on a scale from one to ten, I'd rate the solution at a nine. It's great. I enjoy using it and would recommend it to others. However, I've only really just started to use it over the past year or two and I have nothing to compare it to as I haven't tried out other solutions.

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

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

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.

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

Mostly REST service and web application development on RDBMS products

I have found the new version with annotations and differentiation between SpringMVC and REST Controllers to be most valuable.

Spring MVC has reduced the time spent on building MVC code in Java projects.

The link with UI components could be improved. For example, there could be auto-transformation from Java objects to simple UI components (such as jQuery tables, drop down lists, autocomplete lists), so that the transformation from Java on the server side to UI components is built-in.

I have used this solution since 2008.

I have not encountered any issues with stability so far.

The product has been scaled to hundreds of simultaneous users, without issue.

There is wide support availability on the stack overflow and there is a lot of documentation on the web.

I have used various alternatives, such as: Tapestry, custom Java MVC, and Struts 1.2/2.0

The setup is extremely straightforward for someone with a decent IDE (Eclipse, for example, and some background configuring Spring projects). However, without experience and training on the Spring configuration, the setup could be a nightmare.

I am always the implementation vendor.

I am today able to spin up a Java web service, especially with embedded Tomcat, within hours. This compares with the week or 10 working days it used to take before Spring MVC.

This solution is free. However, do make sure to release any common components that you build back into spring.io.

I evaluated Struts 2.0. However, the Spring-Struts integration would have been troublesome. Hence we went with Spring MVC, for ease of integration.

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.