【Chapter 1】架构模式

Architectural Patterns

• In some cases, architectural elements are composed in ways that solve particular
  problems. The compositions have been found useful over time, and over many
  different domains, and so they have been documented and disseminated. These
  compositions of architectural elements, called architectural patterns, provide
  packaged strategies for solving some of the problems facing a system
  在一些情况下，架构元素按照一定的方式组成以解决特定的问题。这种组成方式在多个领域经过长期的验证是很有用的，因此，它们被记录成档并被广泛传播。
  这种架构元素的组成就称为架构模式，提供了整套策略来解决系统中一些特定的问题。
• An architectural pattern delineates the element types and their forms of interaction used in solving the problem. Patterns can be characterized according to
  the type of architectural elements they use. For example, a common module type
  pattern is this:
  架构模式详细的描述了用于解决问题的元素类型及各元素之间的交互形式。
  模式可以根据它们使用的架构结构元素的类型进行特征描述（分类）。
  例如，常见的模块类型模式有：
  Layered pattern.
  分层模式
• When the uses relation among software elements is
  strictly unidirectional, a system of layers emerges. A layer is a coherent
  set of related functionality. In a strictly layered structure, a layer can only
  use the services of the layer immediately below it. Many variations of this
  pattern, lessening the structural restriction, occur in practice. Layers are
  often designed as abstractions (virtual machines) that hide implementation
  specifics below from the layers above, engendering portability.
  当软件元素之间的使用关系是严格单向的时候，系统分层就出现了。层就是一套相互关联的功能的集合。
  在严格的分层结构中，某层只能调用它自己紧挨着的下层的服务。但是，在实际应用中，这个模式有很多变化以削弱这种结构上的限制。
  层通常被设计成是抽象的（虚拟机）,以便对上面的层隐藏实现，增加了可移植性。

Common component-and-connector type patterns are these:
常见的组件-连接器类型模式有：
Shared-data (or repository) pattern.
数据共享（仓库）模式

• This pattern comprises components
  and connectors that create, store, and access persistent data. The repository
  usually takes the form of a (commercial) database. The connectors are
  protocols for managing the data, such as SQL.
  这种模式由组件和连接器组成用于创建、存储和存取持久化数据。仓库通常采用（商业化）数据库的形式。
  连接器作为管理数据的协议，如SQL。
  Client-server pattern.
  客户端-服务器模式
• The components are the clients and the servers, and
  the connectors are protocols and messages they share among each other to
  carry out the system’s work.
  客户端和服务器称为组件，连接器是协议和消息，它们彼此共享以执行系统的工作

Common allocation patterns include the following:
一般的分配模式有：

Multi-tier pattern
多层模式（物理层）

• which describes how to distribute and allocate the
  components of a system in distinct subsets of hardware and software,
  connected by some communication medium. This pattern specializes the
  generic deployment (software-to-hardware allocation) structure.
  它描述了如何在不同的硬件和软件子集中分配和分配一个系统的组件，这些组件通过一些通信媒介连接。
  此模式专门用于通用的部署(软件到硬件分配)结构。

Competence center and platform
能力中心和平台

• which are patterns that specialize a
  software system’s work assignment structure. In competence center, work
  is allocated to sites depending on the technical or domain expertise located
  at a site. For example, user-interface design is done at a site where usability
  engineering experts are located. In platform, one site is tasked with
  developing reusable core assets of a software product line (see Chapter 25),
  and other sites develop applications that use the core assets.
  这种模式专门用于系统的工作任务分配结构。在能力中心，工作任务分配的地方取决于所将要分配的地方是否有相关的技术或领域上的专家。
  例如，用户界面设计会分配到有可用性工程专家的地方。
  在平台中，一个站点的任务是开发软件产品线的可重用核心资产(参见第25章)，其他站点开发使用核心资产的应用程序。

Architectural patterns will be investigated much further in Chapter 13.
架构模式将在13章进行深入研究。

翻译自《软件架构实践》