I asked a similar question and received a convincing answer?
What is the difference between website development in MVC and a 3-tier or N-tier architecture?
In connection with the completion of this issue, I began to develop projects in the architecture of the N-level.
About an hour ago, I asked another question: what is the best design for creating an interface? There, the most voted answer suggests me using the MVC architecture.
What is the best design template for developing a WebPage interface?
Now I am confused. The first message suggested to me that both of them are similar, just the difference in level N, the level is physically and logically separated, and one layer has access to what is above and below it, but not all layers.
I think ASP.net used a level 3 architecture when developing applications or web applications. If as frameworks such as Zend, Symphony, they use MVC.
I just want to stick with the template that is best for developing WebProject. Maybe this is a very stupid confusion? But if someone can eliminate this confusion, will it be very helpful?
They are not mutually exclusive. The Model-View-Controller pattern is really a user interface design pattern, and it deals with logical rather than physical layers.
"n- ", . , , , (, -), (, ), , , , ( ).
, " " : n- - - (, , ).
, n- -, . - , .
, , (, ).
- MVC, , .
, WebProject ? , ? - , ?
, :
1) , .
, .
2) MVC , .
, , MVC. , -MVC , MVC.
, : .
Microsoft. Microsoft . , :
? . MVC, WebForms ..
- MVC MVC. , ( ) .
AJAX , , "" MVC, , View, "" .
, , . MVC/3, "MVC". -. - , View ( , PHP). , . , , . , , CodeIgniter, Kohana, Symfony, CakePHP Zend, , .
? MVP N-. MVP , .. -. , -, -. - - (BLL), (DAL). DAL Entity Framework.
, . MVP MVC. , (-) , , -. , , .
, . , . , n- . , MVC . , , , .
, . MVC n- , . - /API, - . :
MVC Vs n-level