MVC is the biggest difference in three-tier architectures,, (Controller controllers-MVC for Design view angle)

Reprint: http://blog.csdn.net/csh624366188/article/details/7183872

Of course, you have to understand the differences and linkages between the MVC three-tier architecture:

The three-tier architecture is the most basic project layering result, and MVC is a variant of the three-tier architecture, and MVC is a good development model. First, you need to understand what MVC means, respectively.
M, model layer, is responsible for the interaction of the business logic and the database.
V is the view layer, which is used primarily to display data and submit data
C is the controller, which is used primarily as a capture request and controls request forwarding

Layer three: UI interface layer BLL business logic layer, DAL data access layer, Model entity layer
The M in MVC is not the Model (entity layer) in the three layer, he actually includes the three layers of the Bll,dal,model, which is very important to note, which is the key to the difference between them

It is a bit like this:
Low coupling resistance
Highly reusable and adaptable
Lower life-cycle costs
Rapid deployment
Maintainability
Facilitates the management of software engineering

Of course, the advantages also have shortcomings, that is, the internal structure is complex, not easy to understand, the number of documents, management difficulty naturally also big

MVC design Pattern ...
Three-tier architecture ...
They are subdivided to get: View (UI), BIZ (BLL), DAO (DAL), Entity (Model), Controller
MVC, which unifies the BIZ (BLL), DAO (DAL), model (Entity), is called the model, and gets: View, Controller, models
Layer three in my use has not realized the existence of the controller, is completely: UI, DAO, BLL

They have the same design philosophy: Separating the view design from data persistence, which reduces coupling, is easy to scale, and improves team development efficiency.

Layer three is based on the business logic, and MVC is based on the page to divide

There is no comparability at all.
Actually, I feel good with both of them.

The MVC pattern is a composite design pattern, a solution
Layer three is a software architecture that enables programming via interfaces
Three-tier mode is an architectural pattern, and MVC is a design pattern
Layer three mode is also attributed to deployment mode, MVC can be attributed to presentation mode

------------------------Experience Split Line-------------------------------------------------------------------

The program pays attention to the page design pattern: The mvc+ three layer architecture design is perfect, and realizes the view separation control, but also realizes the background data business logic separation;

MVC, which unifies the BIZ (BLL), DAO (DAL), model (Entity), is called models, and obtains: View, Controller, model;

Cons: View + business logic (mvc+ three-tier architecture) data logic complex (data multi-level interaction), increase the system internal overhead;

Advantages: can realize the realization of the staff full-time (modular development), improve the code reuse ability, make the project more hierarchical sense,

MVC is the biggest difference in three-tier architectures,, (Controller controllers-MVC for Design view angle)