Tuesday, May 26, 2015

I had several people ask me what is the difference between MVC (Model View Controller) and three-ti


I had several people ask me what is the difference between MVC (Model View Controller) and three-tier architectural standards. It is my intention to clear up the confusion by comparing the two models export company side by side. At least in part, I believe the source of some of the confusion is that both have three distinct layers or nodules in their respective diagramas.Se you look closely at each diagram you will see the associations (arrow connectors) between the boxes are set up a bit different. 3 Layers MVC 3 Layers A three-tier system is actually composed of layers (think of the cake layers). The user interface layer has access to the business logic layer and the business layer has access to the data layer. But the user interface layer can not directly access the data layer. So that the user interface layer to access the data, it must go through export company the business logic layer through some kind of interface. If it helps, export company you might think of each layer as a major component of loosely coupled with strict export company design rules of access between the layers. MVC (Model View Controller) In contrast, the MVC pattern, obviously not keep a layered system. Contoller access The Model (a data repository at runtime) and the View. The View then accesses the Model. Exactly how does that work? The driver export company ultimately is the point of logical decision. What kind of logic? Typically, the controller will retrieve, build or modify a model based on some trigger action. The controller then decides it's export company appropriate View via some internal logic. At this point, export company the controller will push the model for display. Note :. Because I mainly export company developing with .NET, Microsoft export company has adopted the standard for ASP.NET MVC with its own platform (see http://www.asp.net/mvc). You can certainly use the MVC pattern without the Microsoft platform, but why reinvent the wheel? export company I have been very happy with it so far. When can I choose which standard? First of all, these two standards are definitely not mutually exclusive. In fact, in my experience, they are quite harmonious. I often use a multi-tiered architecture, as a three-tier architecture for the global architectural structure. Then, within the UI layer, I use MVC. Something like the diagram below.
Lomadee, a new species export company on the web. The biggest platform of affiliates in Latin America.


No comments:

Post a Comment