Spring MVC Reviews

With Spring MVC, I have only developed things based on problems. Spring MVC follows monolithic architectures, and it also includes monorepo. Spring MVC takes care of the implementation of controllers along with areas like controller class and service class. Spring MVC allows me to work with REST APIs, meaning it is an API-based product. Spring MVC basically supports REST API, along with the components and features. With Spring MVC, there is no need to write a lot of code as it supports the boilerplate code. A lot of annotations are used in Spring MVC, and it directly fetches what is required from the package. A user need not rely on an external package as the product automatically fetches what is required from the annotations used in Spring MVC, which makes it much more reliable and faster.

The best feature of Spring MVC is its auto-configuration capabilities. A user need not configure anything in the product as it offers configuration files to set profiling and guide users with what they need to connect for development, staging, or production. The auto-configuration is one of the best components of the solution.

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.

We primarily use the solution to create APIs. Basically, you have a SQL query, and you write Java code to create a single API link based on that. And then, that API gets connected to JasperReports Library using an adapter. You create reports based on that.

The company wanted to create an API hub. And then whatever they needed to access, they wanted to access it from that central API to be able to do anything with the data. That way, when an API was required, they used Spring MVC to be able to create that API. On the back-end side, it was Oracle 11G that needed to retrieve the data for the specific API.

MVC would have been beneficial if, at all, we needed to, let's say, add any customizers on top of it. For example, if at all you need is some sort of logic to be applied to a specific report, which is not available in, let's say, JasperReports Library.

I could write this MVC code or could use a scriptlet, which is a feature in the JasperReports engine, to be able to write the classes on top of it. Or I would use an MVC model to pass those values to be able to get the results based on the requirements.

There are a lot of dependencies during the initial setup.

We mainly use the solution to create microservices and functional services as rest services, which expose services at rest. In case there are things to orchestrate or to implement some flows, we can use other sub-projects like Data Flow, but Spring MVC's main use case is to explore capabilities to rest services so they can be used by the upper layer, which is the frontend.

It's an enterprise platform that's widely adopted. The platform has a large community, and you'll easily get support. Spring has extensive support for security because of frequent updates.

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.

I work for a financial institution that has a payment app in Pakistan. I can't be specific about how we use Spring MVC, but it is generally used for microservices.  

Spring MVC is fast and reliable. 

I use the solution to write APIs.

Spring MVC has provided me with a simple way to access my solution using a layered pattern.

We use this solution for creating web applications, and for linking our UI with the backend of the system.

We appreciate that this product is really easy to integrate with third-party UI services.

This solution is also very straightforward for new users wishing to create items.