What is the difference between developing a website in MVC and 3-Tier or N-Tier architecture?
Which of the following is better? What are professional and cons?
They are very similar, although the top-level (presentation) in the 3-level directly follows the level Data firmness) does not directly contact with.
In the model-view-controller, theoretically the 'model' should be 'informed' so that it has changed so that it can change the view as updated, however, it is usually not a problem in most web applications Because they are stateless I'm not sure that there are visuals of any famous PHP MVC architecture that communicate directly with the model or vice versa, but if they do not do it Hanna will find that they are actually 3-tier.
Wikipedia says:
At first glance, three levels may look similar to MVC (Model View Controller) concept; However, topologically they are different, a basic rule in the three-level architecture does not directly contact customer level data levels; In a three-level model, all communications must undergo middleware level. Conceptually three-level architecture is linear, however, the MVC architecture is triangular: the view sends updates to the controller, updates the controller model, and the view updates directly from the model.
Source:
Comments
Post a Comment