MVC中的3层架构 [英] 3 tier architecture in MVC

问题描述

3tier架构和mvc有什么区别。并且可以在MVC中使用3层架构。



亲切的建议



我尝试了什么：



i已经开发了3层架构。和mvc中的beginer可以在mvc中使用3层。什么是优点和缺点

what is the difference between 3tier architecture and mvc . and can use 3 tier architecture in MVC.

kindly suggest

What I have tried:

i have worked on 3 tier architecture. and beginer in mvc can use 3 tier in mvc. what are the advantage and disadvantage

推荐答案

这就像比较苹果和橘子。 MVC是一个表示框架，它将显示数据的各个部分分开（分为表示数据的模型，显示它的视图和作为两者之间接口的控制器），而3tier体系结构允许您将功能划分为多个层。可以是逻辑层（即所有组件都在同一个项目中）或分成物理层并在不同的机器上运行。



谷歌并阅读两者并在您了解时他们都应该理解他们的不同之处。

That's like comparing apples and oranges. MVC is a presentation framework that separates the various parts of displaying the data (into model which represents the data, the view which shows it and the controller which is the interface between the two) whereas 3tier architecture allows you to divide your functionality into layers that can be logical layers (ie components all in the same project) or divided into physical layers and run on different machines.

Google and read up on both and when you understand them both you should understand how they differ.

这篇关于MVC中的3层架构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！