MVC pros and cons

1. Make complex projects easier to maintain by dividing the project into model View and controller.

2. The view state and server form controls are not used, which makes it easier to control the behavior of the application

3. The application uses a controller to control the request and can provide a rich URL rewrite.

4. Better support for unit testing

5. Better performance in team development mode

the lack of MVC:

(1) Increase the complexity of the system structure and implementation. For a simple interface, strict adherence to MVC, which separates the model, view, and controller, increases the complexity of the structure and may result in excessive update operations and reduced operational efficiency.
(2) The connection between the view and the controller is too tight. Views and controllers are separated from each other, but they do have a tight connection, the view has no controller, its application is very limited, and vice versa, which prevents them from being reused independently.
(3) A view of inefficient access to model data. Depending on the model operator interface, the view may need to be called multiple times to obtain sufficient display data. Unnecessary frequent access to unchanged data will also compromise operational performance.

MVC pros and cons