Difference Between 3 Tire Architecture and MVC Pattern

First take 3 tire Architecture:-

 

Now come on MVC:-

  • While MVC is an application architecture pattern.
  • whereas with MVC, everything will most likely be on one system
  • Whereas MVC comes from the previous decade (by work at Xerox PARC in the late 1970s and early 1980s)

Conclusion:-

MVC is a pattern for structuring your UI-layer code, while a three tier architecture is about how your hardware is laid out.


MVC is about separating the request processing code from the state (model) code and from the display (view) code. The three all worth together to deal with a user interaction, but the pieces have distinct
roles and are typically best served to be segregated based on those roles.

Three tier architecture is about physically separating your presentation code (typically an MVC application) from your business logic (typically a set of business objects) and your persistence layer
(a database) onto different hardware.  The advantages are that the three layers can then scale independently and that they can have different network security policies wrapped around them.

A fundamental rule in three-tier architecture is the client tier never communicates directly with the data tier; in a three-tier model all communication must pass through the middleware tier.
It’s liner architecture. This addresses the question of how to pass information between a user and a database. Whereas MVC is a triangular architecture: the View sends updates to the Controller, the Controller updates the Model, and the View gets updated directly from the Model. This addresses questions of how a user interface manages the components on the screen.

Conceptually the three-tier architecture is linear. However, the MVC architecture is triangular: the view sends updates to the controller, the controller updates the model, and the view gets updated directly from the model.

From a historical perspective the three-tier architecture concept emerged in the 1990s from observations of distributed systems (e.g., web applications) where the client, middleware and data tiers ran on physically separate platforms. Whereas MVC comes from the previous decade (by work at Xerox PARC in the late 1970s and early 1980s) and is based on observations of applications that ran on a single graphical workstation; MVC was applied to distributed applications much later in its history

Conclusion:-

MVC is a pattern for structuring your UI-layer code, while a threetier architecture is about how your hardware is laid out.

MVC is about separating the request processing code from the state (model) code and from the display (view) code. The three all worth together to deal with a user interaction, but the pieces have distinct
roles and are typically best served to be segregated based on those roles.
Three tier architecture is about physically separating your presentation code (typically an MVC application) from your business logic (typically a set of business objects) and your persistence layer
(a database) onto different hardware.The advantages are that the three layers can then scale independently and that they can have different network security policies wrapped around them.
A fundamental rule in three-tier architecture is the client tier never communicates directly with the data tier; in a three-tier model all communication must pass through the middleware tier.
It’s liner architecture. This addresses the question of how to pass information between a user and a database. Whereas MVC is a triangular architecture: the View sends updates to the Controller, the Controller updates the Model, and the View gets updated directly from the Model. This addresses questions of how a user interface manages the components on the screen.

Conceptually the three-tier architecture is linear. However, the MVC architecture is triangular: the view sends updates to the controller, the controller updates the model, and the view gets updated directly from the model.

From a historical perspective the three-tier architecture concept emerged in the 1990s from observations of distributed systems (e.g., web applications) where the client, middleware and data tiers ran on physically separate platforms. Whereas MVC comes from the previous decade (by work at Xerox PARC in the late 1970s and early 1980s) and is based on observations of applications that ran on a single graphical workstation; MVC was applied to distributed applications much later in its history

About Krishana Kumar

Krishana Kumar is SharePoint Architect/Trainer having Architecture experience with high volumes at Enterprise level and global scale - creation of highly scalable solutions with global user base and geographically distributed architectural components. Good knowledge of SharePoint best practices and governance models. I hold Two Master degree in Computer Science with over 11 years of experience working on Microsoft Technologies specially SharePoint, Project, .NET and other Information Worker Technologies. Having good exposer in Client side scripting Angular.js, backbone and Node. I am currently responsible for SharePoint Infrastructure set up and leading teams in various medium and large scale projects, architecting, designing & installing SharePoint farms, developing custom components,, and providing advanced SharePoint administration and development training to teams and customers. I regularly speaks in various SharePoint User Groups and other Events. I have MCSA Windows Azure, MCSA Office 365, MCSE & MCSD SharePoint 2013, Microsoft Certified Developer (MCD) and holds MCPD, MCTIP and MCTS for SharePoint 2010, MCTS MOSS 2007 & WSS 3.0, MCPD, MCITP (EPM 2010 & 2007) and MCSD .NET.
This entry was posted in Research - Search again... Bookmark the permalink.