Figure 6 depicts this architecture.
图6描绘了此体系结构。
In this architecture, each server contributes equally.
在这种体系结构中，每个服务器的作用相同。
The Diagram below shows how this architecture would work.
下述图表展示了此架构是如何工作的。
Here are the basic functional units of this architecture.
以下是这种体系结构的基本功能单元。
Figure 1 shows the logical model view of this architecture.
图1显示了此体系结构的逻辑模型视图。
This completes the sample implementation of this architecture.
这样，该体系结构的样本实现就结束了。
There are a number of useful ways to visualise this architecture.
有很多有用的方法来形象表示该架构。
To deploy to this architecture, no project Settings need to be changed.
部署这种体系结构不需要更改项目设置。
The two big ideas in this architecture are channels and bindings [...].
这种体系架构最突出的两个理念就是通道与绑定[…]。
We're pleased to introduce this architecture improvement so that you can benefit.
我们很高兴引入了这个架构改进，让您能够受益。
However, even in a best-case scenario, this architecture can cause deadlock issues.
然而，即使是在最好的情况下，这个架构仍然会引起死锁问题。
Services: Create the architecture for an SOA system (services are central to this architecture).
服务：为一个SOA系统创建架构(服务是该架构的中心)。
The component interaction of the system defined by this architecture is illustrated in Figure 4.
这个架构定义的系统的组件交互在图 4 中展示。
In this architecture extension modules, (UIMA plug-ins, in other words) are also called annotators.
在这个体系结构中，扩展模块(换句话说，是UIMA插件)也称为注解器。
In its most basic form, this architecture can be broken down into three tiers: front, mid, and database.
按照最基本的形式，这个体系结构可以分为三层：前端层、中间层和数据库层。
In this architecture, the consumer never communicates with the service directly, only through the intermediary.
在这种体系架构中，客户从不与服务直接通信，只是通过中介来实现交互。
In this architecture, different types of components are all viewed as services and can be accessed the same way.
在这个体系结构中，不同类型的组件都被看作服务，并且可使用相同的方式进行访问。
But this architecture must be sufficiently abstract to fit the large range of designs we are likely to encounter.
但是该架构必须足够抽象，以适应我们很可能遇到的大范围的设计。
In this architecture, we leverage WebSEAL's ability to perform SPNEGO authentication on incoming Web connections.
在此体系结构中，我们利用WebSEAL的功能来对传入Web连接执行SPNEGO身份验证。
A common example of this architecture is a Web browser that behaves as a client when a URL is requested over HTTP.
这种架构的一个常见例子就是Web浏览器，当通过HTTP请求url时，Web浏览器就相当于一个客户端。
In the last decade, it industry has made tremendous advances in understanding and improving this architecture style.
在过去的10年间，IT界在理解和改进这种架构风格上已经取得了显著的进步。
The nature of this architecture is highly complex and requires a high degree of integration of hardware and software.
这种架构的特点是高度复杂，并且要求硬件和软件的高度集成。
The general traits of WebSphere DataStage jobs that are likely to benefit from this architecture are then summarized.
接着，本文总结有望从这种架构中获益的WebSphereDataStage 作业的一些特征。
Microsoft itself does not have an assembly mechanism so you cannot even implement this architecture blueprint in .Net.
微软本身并没有装配机制，因此你甚至不能在.Net中实现这个架构蓝图。
With this architecture, DSL gets invoked for every data access operation or transaction initiated by a business service.
使用这个体系架构，业务服务发起的每个数据访问操作或事务都将调用DSL。
In this architecture, an IPSec router in the client infrastructure encrypts traffic bound for the service infrastructure.
在此体系结构中，客户端基础结构中的ipsec路由器对发往服务基础结构的通信进行加密。
But the prerequisite of this architecture change is IDS 9.40; it would be totally impossible with previous versions of IDS.
但是此体系结构的先决条件是IDS 9.40；若使用IDS的以前版本，这将是完全不可能的。
To implement this architecture, there are dedicated companies supporting car manufacturers for one or more of these modules.
要实现这个架构，有专门的汽车配套产品制造商来提供一个或多个这种模块。
In this architecture, no processing in done at the code server. The client connectivity code is simply loaded from a code server.
在这种架构中，代码服务器中不会执行任何处理，而只是从其中加载客户机连通性代码。
However, as previously noted, in this architecture, there are two pieces of circuitry that are used to execute compute instructions.
然而，如前所述，在这种架构中，有两块电路用于执行计算指令。
应用推荐