N层应用程序 - 设计问题 [英] N-tier application - Design issue
问题描述
嗨大家好，
在N层应用程序中，N ???的可能值是多少？我不是开玩笑，我今天刚接受程序员的采访，他开始使用
2层应用程序。会话。从那时起，我听说5层
申请然后是7层应用程序....我知道什么是
3层应用程序，但是2,5和7呢??? 2层是否意味着
客户端 - 服务器应用模型？ 5和7怎么样???
请你把这个描述一下吗？
TIA，
Mehdi
Hi folks,
In an N-tier application, what is the possible values of N??? I''m not
kidding, I just interviewed with a programmer today, and he started the
"2-tier application" conversation. From then on, I heard about "5-tier
application" and then "7-tier application".... I do know what is a
3-tier application, but what about 2, 5, and 7??? Does 2-tier means a
"Client-Server" application model? What about 5 and 7???
Would you please describe me this?
TIA,
Mehdi
推荐答案
2层是客户端服务器，要么是胖子的大部分逻辑，要么是b $ b客户端，或通过瘦客户端访问的服务器。
3层是经典的客户端 - 服务器 - 数据库架构，其中
客户端的工作看起来很漂亮但是在服务器上处理所有业务逻辑
，将数据库隐藏在远离用户的位置，验证
的东西，应用业务规则等。
2 tier is client server, either with the majority of the logic on a fat
client, or on the server accessed through a thin client.
3 tier is the classic client - server - database architecture where the
client''s job is to look pretty but all the business logic is processed
at the server which hides the database away from the user, validates
stuff, applies business rules, etc.
>从那里开始，每个额外的层通常是将
>From there each additional tier is generally a way of breaking the
服务器分解为谨慎部分的方法。例如，数据访问层管理
与数据库的所有通信，而业务规则层将实现业务逻辑。这提供了这样的优势：如果您希望将数据访问层替换为与不同数据库通信的数据访问层，则可以单独处理数据访问层
知道你不会损害你的业务规则。
在客户端，你可以有一个演示文稿抽象层，
定义如何应用程序应该看起来和感觉无论是否它是作为aspx或Windows窗体应用程序运行。
添加一个层来分发服务器请求，所以你可以有两个
或更多的服务器作为一个无缝应用程序，至少
五层。
mehdi_mousavi写道：
server into discreet sections. A data access tier for example manages
all communication with the database while a business rules tier would
implement business logic. This offers the advantage that if you wanted
to replace the data access tier with one that communicates with a
different database, you can work on the data access tier in isolation
knowing you won''t damage your business rules.
On the client end, you can have a presentation abstraction tier which
defines how an application should look and feel regardless of whether
it''s running as aspx or a windows forms app.
Add in a tier for distribution of server requests, so you can have two
or more servers acting as one seamless application, that''s at least
five tiers.
mehdi_mousavi wrote:
嗨伙计们，
在N层应用程序中，N ???的可能值是多少？我不是开玩笑，我今天刚接受程序员的采访，他开始使用
2层应用程序。会话。从那时起，我听说5层
申请然后是7层应用程序....我知道什么是
3层应用程序，但是2,5和7呢??? 2层是否意味着
客户端 - 服务器应用模型？ 5和7怎么样???
请你把这个描述一下吗？
TIA，
Mehdi
Hi folks,
In an N-tier application, what is the possible values of N??? I''m not
kidding, I just interviewed with a programmer today, and he started the
"2-tier application" conversation. From then on, I heard about "5-tier
application" and then "7-tier application".... I do know what is a
3-tier application, but what about 2, 5, and 7??? Does 2-tier means a
"Client-Server" application model? What about 5 and 7???
Would you please describe me this?
TIA,
Mehdi
DeveloperX写道：
Hi,
DeveloperX wrote:
2层是客户端服务器，可以是胖客户端的大部分逻辑，也可以是通过瘦客户端访问的服务器。
2 tier is client server, either with the majority of the logic on a fat
client, or on the server accessed through a thin client.
我认为非瘦客户的政治正确用语是厚的b $ b客户;-)
Laurent
-
Laurent Bugnion，GalaSoft
软件工程： http://www.galasoft-LB.ch
PhotoAlbum： http://www.galasoft-LB.ch/pictures
支持加尔各答的儿童： http://www.calcutta-espoir.ch
I think the politically correct term for a non-thin client is a "thick"
client ;-)
Laurent
--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch
我认为非瘦客户端的政治正确术语是厚的。
I think the politically correct term for a non-thin client is a "thick"
client ;-)
client ;-)
那么FAT32呢？ THICK32？
- 抱歉，无法抗拒:-)
-
关于
Anders Borum / SphereWorks
微软认证专家（.NET MCP）
What about FAT32 then? THICK32?
- sorry, couldn''t resist :-)
--
With regards
Anders Borum / SphereWorks
Microsoft Certified Professional (.NET MCP)
这篇关于N层应用程序 - 设计问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
