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.
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.
Java Software Engineer (Future Innovator) at Telenor Microfinance Bank (TMB)
Real User
Top 5
2023-03-29T10:03:07Z
Mar 29, 2023
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.
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.
Technical Development Lead at a government with 1,001-5,000 employees
Real User
Top 10
2022-05-18T14:14:19Z
May 18, 2022
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.
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.
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.
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 MVC, View Technologies, CORS Support, and WebSocket Support.
For baseline information and compatibility with Servlet container and Java EE version ranges please visit the Spring...
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.
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.
Our primary use case is only for developing business web applications.
We use the solution for the development of our web applications.
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.
I use the solution to write APIs.
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.
We use this solution for creating web applications, and for linking our UI with the backend of the system.
I use Spring MVC for applications on the web.
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.
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.
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.
We're primarily using the solution to develop the content, web pages, and data system. We then suggest our system to our customers.