Imagine that you have completed your CodeGym training and are looking for your first job. In job descriptions, you come across frameworks and tools that you have not gone through. We are starting a series of articles to help you understand which Java tools are used in which projects, and at what stage in a developer's career they should be taught. In the third article, we will talk about the Spring MVC framework.
Spring MVC: what is it?
Spring MVC is a component or design pattern of the Spring Framework that allows you to develop web applications in Java using the Model-View-Controller architecture. The Model - View - Controller architecture consists of three components, which are embodied in its name. The Model component implies the logic of working with data, the View - the logic of the interface, the Controller - the logic of processing requests. Simply put, the Controller receives data from the Model and then displays this data in the View (view - ed.). The Controller also processes requests from the user and redirects him to the necessary pages of the application. The website page is the View component that the user sees.It is important to understand that all Spring MVC components are clearly separated from each other. The operation of this design pattern can be compared to the operation of a restaurant, where the kitchen is the Model, the waiters are the Controller, and the View is the hall of the restaurant, where the orders received by the visitors are placed. Kitchen workers do not intersect with visitors, just as visitors do not enter the kitchen, and only the Controller, that is, waiters, can receive orders and transfer them to the kitchen, and then take orders to the service hall. All Spring MVC components are loosely coupled and, if desired, we can change, for example, the appearance of the application without making significant changes to the other two components.
How popular is Spring MVC?
It is worth considering that Spring MVC is not as often indicated in job descriptions as, for example, Spring Boot. However, research on IT recruiters also has this design pattern. For example, the CV Compiler resource, after processing 300 vacancies for Java developers from sites such as AngelList, StackOverflow, LinkedIn, reported that most companies prefer to create the back end of their web applications using Spring MVC . The average salary of developers who own Spring MVC is about 55 thousand pounds (about 73 thousand dollars) per year, according to ITJobsWatch .
What projects will you need?
On many, where you need to create web applications. Of course, you can use various parts of Spring in web applications, not just Spring MVC, but knowing this design pattern will not be superfluous.
When and how to teach?
Before you learn Spring MVC, you should master the Java base and the Spring Framework. That is, starting to learn the Spring Framework, you can simultaneously master Spring MVC. This design pattern is also studied in the CodeGym internship. You can learn the basics of Spring MVC in a month or less. The main thing is to remember how the design pattern works. “Knowing only the MVC module is useless. First you need to learn the core of Spring and dependency injection. I would also learn Spring Boot before that, ”says developer Bruno Mendola .
It is important to understand that all Spring MVC components are clearly separated from each other. The operation of this design pattern can be compared to the operation of a restaurant, where the kitchen is the Model, the waiters are the Controller, and the View is the hall of the restaurant, where the orders received by the visitors are placed. Kitchen workers do not intersect with visitors, just as visitors do not enter the kitchen, and only the Controller, that is, waiters, can receive orders and transfer them to the kitchen, and then take orders to the service hall. All Spring MVC components are loosely coupled and, if desired, we can change, for example, the appearance of the application without making significant changes to the other two components.
GO TO FULL VERSION