4层(对于N层)体系结构的示例? [英] Example of 4-Tier (for N-Tier) Architecture?

问题描述

最近，我的一个朋友向我询问了有关N-Tier体系结构的信息，我能够通过示例向他解释大约1、2和3层体系结构.但是当我想举三个以上的例子时，我陷入了困境.我用谷歌搜索并寻求帮助，但找不到任何合适的例子.

Recently a friend of mine asked me about N-Tier architectures and I was able to explain to him about 1, 2 and 3 tier architectures with examples. But I was stuck when I wanted to give examples for more than 3 tiers. I googled and binged for help, but could not find any decent examples.

它被命名为N层的事实使我认为'N'可以是从1开始的任何数字.但是我找不到4层或5层的任何示例.

The fact that it is named N-tier makes me think that 'N' can be any number starting from 1. But I couldn't find any examples for 4 or 5 tier.

有人可以分享一些涉及3层以上的N层架构的例子吗?

Can somebody share some examples of N-tier architectures that involves more than 3 tiers?

推荐答案

1. 基本服务:例如数据库，目录服务，文件和打印服务，硬件抽象.该层越来越被称为平台.
2. 业务域层:包括EJB，DCOM或CORBA服务对象的JavaEE之类的应用服务器.通过使用SOA和微服务来提供业务功能，并不断增加.
3. 演示层:例如Java Servlet/JSP，ASP，PHP.该层将越来越多地包含WebServices作为业务层服务的代理和适配器.
4. 客户端层:瘦客户端(如浏览器上的HTML页面)和富客户端(如Java WebStart&闪光.
   • 在Java EE中，通常将业务域层划分为数据访问(实体Bean)和商业服务(会话Bean).
   • 在企业SOA(面向服务的体系结构)中，ESB通常作为第1层和第2层之间的附加层存在. 2.它可能是平台规定的一部分.
   • 在混搭中，您可以在第3层和第2层之间建立一个聚合层. 4.

1. Fundamental Services : e.g. Database, Directory Services, File & Print Services, Hardware abstraction. This tier is increasingly called the platform.
2. Business Domain Tier : An Application Server such JavaEE including EJB, DCOM or CORBA Service Objects. Provide business functionality, increasing using SOA and Micro-services.
3. Presentation Tier : e.g. Java Servlets/JSP, ASP, PHP. This tier will increasingly include WebServices as proxies and adaptors for business tier services.
4. Client Tier : Thin clients like HTML Pages on Browsers and Rich Clients like Java WebStart & Flash.
   • In Java EE it is common to divide the Business Domain tier into Data-Access (Entity Beans) & Business Services (Session Beans).
   • In an Enterprise SOA (Service Oriented architecture) the ESB would typically exist as an additional tier between tiers 1 & 2. It may be part of the platform provision.
   • In Mashups you could have an aggregation tier between tier 3 & 4.

被称为N-Tier的举动反映了从越来越老的客户端服务器到最初的3层，然后是4层，向组件化架构的转变的趋势.层的定义特征是清晰定义的界面，其中包含关注点分离.

The move to being called N-Tier is a reflection of the move to increasingly componentised architectures from the older client-server to first 3-Tier then 4-Tier. The defining characteristic of a tier is a clearly defined interface with a separation of concerns.

这篇关于4层(对于N层)体系结构的示例?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！