MVC and three-tier architecture
(The wrong words welcome to Spray, no baggage)
First, the concept
1. MVC Initial concept input (Controller), output (view), logical processing (model)
The 2, three layer architecture is a further division of the logical processing layer (model layer) in the original MVC concept, ui-the business logic bll-data Access DAL. The model in layer three is the data model, which corresponds to the database
But today MVC is almost as much a concept as the three layer.
Second, the comparison between the two:
1, the two layered thinking the same
2, the purpose is conducive to the division of Labor
3, are conducive to the module (code block) reuse, code reuse the popular understanding of the individual is a mashup, the example of life: one-piece clothing inseparable, divided into the upper and lower clothing (module) to achieve more combinations;
The dress is replaced with an upper and lower garment called decoupling
4. MVC-architecture level; Three layers-the division of functional modules in software engineering level, a design pattern of soft project, follow the MVC thought
Add:
The level of ASP. NET MVC and WebForm can not be misunderstood because of the name of an MVC.
It's just a further subdivision of the UI layer (the output layer) within the three-layer concept, which is a framework of the UI layer;
Whether using ASP, ASP, WinForm or WebForm, the business logic and data access layer are implemented with class libraries;
C # Learning Note 2