【Chapter 1】架构结构之间的关系及选用

架构结构之间的关系及选用

• Relating Structures to Each Other
  各个结构之间是相互关联的
• Each of these structures provides a different perspective and design handle on a
  system, and each is valid and useful in its own right. Although the structures give
  different system perspectives, they are not independent. Elements of one structure
  will be related to elements of other structures, and we need to reason about these
  relations.
  每种结构都为系统提供了不同的视图和设计，并且每种结构都有其自身的有效性及实用性。尽管，这些结构都给出了系统的
  不同视角，但是它们并不是相互独立的。一种结构的元素都会与其他结构的元素相关联，并且，我们需要去推理这些关系。
• For example, a module in a decomposition structure may be manifested
  as one, part of one, or several components in one of the component-and-connector structures, reflecting its runtime alter ego. In general, mappings between
  structures are many to many.
  例如，模块结构的子结构分解结构可以是组件-连接器结构中的一个、部分或者几个组件，反映其运行时的另一个自我。一般来讲，结构之间的映射关系是多对多的。

Fewer Is Better
越少越好

• Not all systems warrant consideration of many architectural structures. The larger
  the system, the more dramatic the difference between these structures tends to be;
  but for small systems we can often get by with fewer. Instead of working with
  each of several component-and-connector structures, usually a single one will do.
  If there is only one process, then the process structure collapses to a single node
  and need not be explicitly represented in the design. If there is to be no distribution (that is, if the system is implemented on a single processor),
  then the deployment structure is trivial and need not be considered further. In general, design and
  document a structure only if doing so brings a positive return on the investment,
  usually in terms of decreased development or maintenance costs
  不是说有的系统都需要考虑许多架构结构。系统越大，各个结构之间的动态差异性就越多；相反，小系统的各个结构之间的差异性就少很多。
  小系统不像大系统那样需要多个组件-连接器结构，通常一个结构就可以了。
  如果只用一个进程，进程有只分解成一个节点，那就不需要在设计中明确表示。如果不需要分布式（也就是说，系统是在单个处理器上实现的），
  那部署结构就很简单了，也不需要更长远的考虑。
  一般来讲，只有设计和记录结构能够带来好的回报时才值得去做，如减少开发和维护的成本。

Which Structures to Choose?
应该选择哪种结构

• Chapter 18 will treat this topic in more depth, but for now a good answer is that you should think about how the various structures available to you provide insight and leverage
  into the system’s most important quality attributes, and then choose the ones that
  will play the best role in delivering those attributes.
  18章将会深入研究这个主题，目前比较好的回答是你应该考虑这些各种各样的结构是如何为你提供洞察系统最重要的质量属性的能力以及这些结构是如何对系统的质量属性产生影响的，然后，谁能最大限度的交付这些属性，就选择谁。

本文翻译自《软件架构实践》