Introduction to MVC

The full name is the Model view controller, models-view-controller, a software design paradigm that organizes the code with a separate approach to business logic, data, and interfaces, and aggregates business logic into a single component, while improving and personalizing the interface and user interaction, There is no need to rewrite business logic.

M refers to the business model, v refers to the user interface, C is the controller, the purpose of using MVC is to separate m and v implementation code, so that the same program can use different representations.

model is the part of your application that handles application data logic.
Typically, model objects are responsible for accessing data in the database. View is the part of the application that handles the display of data.
Typically views are created from model data. A controller is a part of an application that handles user interaction.
Usually the controller is responsible for reading data from the view, controlling user input, and sending data to the model. MVC layering helps you manage complex applications because you can focus on one aspect at a time. For example, you can focus on view design without relying on business logic. It also makes testing of applications easier. The MVC hierarchy also simplifies group development. Different developers can develop views, controller logic, and business logic at the same time. The first time you see this word is when you know Django, think long (but you don't write Django now) from Baidu Encyclopedia

Introduction to MVC