Talking about MVC and L3 architecture in my eyes

First, I will elaborate on the well-known concepts. MVC refers to model, view, and controler. Three Layers refer to the UI Layer (or view layer), BL layer, and DA layer.
In common: both have three elements, both have a view, and there is also a model class library on the common layer-3.
Differences: layer-3 architecture and MVC development model. In this case, you may still not understand it. For example, just like building a house, you need to build several layers first. This is the architecture, whether each layer uses single-span beams or multiple-span beams is the mode.
The architecture is fundamental and unified. Once determined, it cannot be modified at will. Otherwise, it is like a layer-3 foundation with four layers, which is prone to problems;
The model is instructive and can be controlled and adjusted according to the actual situation during the implementation process. For example, if multiple cross beams are used for each layer of the plan, it is found that the single cross girder can also meet the needs of the third layer during implementation, after approval, you can proceed with the new plan.
Because ASP. the MVC example of net implements the entire solution using MVC. As a result, some people think that the project either uses MVC or N layers. In fact, the two should not be so opposite, as a result, the model of MVC is too large to be easily managed. We can segment the model in MVC, for example, into the UI logic layer (responsible for data verification and input/output management with the keyboard and mouse) business logic layer (responsible for organizing and processing business data) and data persistence layer. On the other hand, we can implement the three-layer UI Layer and Bl layer in the MVC mode.
Note: The above comments are my family's words. The purpose is to welcome everyone to discuss and correct them. Thank you very much!