是这个3层架构还是其他什么？ [英] is this 3-tier architecture or anything else?

问题描述

这里有点混乱，因为我是3层架构的新手。





我认为如果是网络应用程序（例如：asp.net空Web应用程序）



BusinessLogicLayer（classlibrary），DataAccessLayer（classlibrary），称为3层架构。



和iam在互联网上的许多文章中搜索他们说三层架构可以有1.Asp.net Web应用程序2.BusinessObjects 3.BusinessLogicLayer

4 .DataAccessLayer但Stil它被称为3层架构。



这里两个被称为3层架构为什么？。可以添加到3层架构的项目数量。

Here i have a little confusion because i'am new to 3-tier architecture.


iam thinking that if a webapplication(ex: asp.net empty Webapplication) have

BusinessLogicLayer(classlibrary),DataAccessLayer(classlibrary), that is called 3 tier architecture.

and iam searched in many articles in internet that they are stating that 3-tier architecture can have 1.Asp.net Web Application 2.BusinessObjects 3.BusinessLogicLayer
4.DataAccessLayer But Stil it is called 3 Tier-Architecture.

Here both are called as 3-tier architecture why?. how many projects that can be added to 3 tier architecture.

推荐答案

层和层之间也感到困惑...

层是关于应用程序的物理分布 - 意味着不同的部分（如Web服务器，数据库服务器等）物理上位于不同的地方...

层是关于应用程序的逻辑分割 - 你在问题中谈到的是什么。

为了说清楚多层应用程序肯定是多层的，但多层应用程序也不一定是多层的！

层/层的正确编号是无关紧要的 - 它可以被称为n层或3层（n层或3层）并且大致相同 - 分离！所以不要让名字（数字）让你感到困惑......

You are also confused between layer and tier...
Tier is about the physical distribution of an application - meaning that different parts (like web server, DB server and so on) are located physically in different places...
Layers are about the logical split of your application - and that what you are talking about in your question.
To make it clear a multi-tier application is for sure a multi-layer too, but a multi-layer application not necessarily multi-tier too!
The proper numbering of tiers/layers are irrelevant - it can be called n-tier or 3-tier (n-layer or 3-layer) and all about the same - separation! So do not let the names (numbers) confuse you...

你可以根据需要添加任意数量的项目。三级提名与您的解决方案中的项目数量无关。它表示接口类（您的视图，页面，表单），业务逻辑（应用程序规则和实体）和数据访问层（您的存储库，数据库，XML或其他）的分离



在上面的示例中，层级将是

层1.Asp.net网页

层2.业务对象和业务逻辑
等级3.数据访问



我希望这可以清除一下这个主题。

You can add as many projects as you want. Three tier nomination has nothing to do with number of projects in your solution. It represents the separation of interface classes (your views, pages, forms), business logic (the application rules and entities) and data access layer (your repository, be it database, XML or something else)

In you example above tiers would be
tier 1. Asp.net web pages
tier 2. business objects and business logic
tier 3. data access

I hope this clears the subject a bit.

这篇关于是这个3层架构还是其他什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！