What is the difference between MVC and three-tier architecture?

First of all, declare that layer three is layer three, MVC is MVC, and these two are irrelevant.

Layer Three is a layer of three from the perspective of the entire application architecture (and can be layered if the program requires it).

A three-tier architecture typically includes a presentation layer, a business logic layer, and a data access layer. Although the three-tier architecture divides the system logically into three layers, it is not a physical layering. That is, for different layers of code, after the compilation, packaging, and deployment, all the code eventually runs in the same process.

MVC is a few modules of different functions that are divided in the view layer of the application (BS structure).

MVC is mainly to solve the application user interface style substitution problem, the Display data HTML page as far as possible and business code separation. MVC separates the Pure Interface presentation logic (user interface) into some files (views), puts some program logic (Controller) that interacts with the user in a few files, passes the data in views and controllers and uses some entity objects that specifically encapsulate the data. These objects, collectively referred to as models.

Only so MVC has nothing to do with layer three because they use different scopes: three layers can be applied to any language, any technology application, and MVC is just to solve the coupling of the parts of the BS application View layer. They are non-conflicting, can exist at the same time, and can be used depending on the situation.

For, for our Java developers:

The three-tier architecture is composed of the interface layer (UI) business Logic Layer (BLL) and the data Access Layer (DAL), and the MVC design pattern is composed of the model layer (M) interface layer (View) and the control layer (Controller), and they do not correspond to each other.

As shown in the following:

is not immediately feel the world is clear, on the stratification and in-depth understanding of a step.

Yang School

Source: http://www.cnblogs.com/xiaoxiao5016

Sharing is happy, but also witnessed the personal growth process, the article is mostly work experience summary and usually learn to accumulate, based on their own cognitive deficiencies are unavoidable, also please correct, common progress.

This article is copyrighted by the author, welcome reprint, but without the consent of the author must retain this paragraph statement, and in the article page obvious location, if there is a problem, can mail ([email protected]) Consulting.

Good text to the top of my attention

What is the difference between MVC and three-tier architecture?