为了交互对象之间的松耦合设计而努力！
Strive for loosely coupled designs between objects that interact.
服务操作能够被设计用作输入、输出、和错误消息，但是这并不是必须的，而且还将导致不合需要的邮戳数据耦合。
Service operations can be designed to use single input, output, and fault messages, but this is not necessary, and can result in undesirable stamp data coupling.
我介绍了与基础设施的耦合及其对设计的不利影响。
I covered coupling to infrastructure and the damage it entails for your design.
这种接口设计到实现类型的耦合性，可能约束soa解决方案所要支持的业务敏捷性。
This coupling of interface design to implementation type could inhibit the very business agility that SOA solutions are intended to support.
只要您可以维持那种关系，您就能避免把自己的代码耦合到基础设施中去，这使您能够更轻易地改变架构和设计。
As long as you can maintain that relationship, you prevent coupling your code to the infrastructure, allowing you to make changes to both architecture and design more easily.
这个应用程序的设计原则是消除视图和模型之间的耦合。
The general design of the application is to remove the coupling of the view from the model.
SOA需要高级别的技术优势和设计，因为它要求松耦合、可使用性和抽象。
SOA demands a high level of technical excellence and design because it demands loose coupling, reusability and abstraction.
轻量级设计模式使您可以在对象和集成服务之间进行松散耦合，而无需艰苦地编写业务逻辑或领域模型。
Lightweight design patterns let you loosen coupling between objects and integrate services without forcing code into business logic or the domain model.
最佳选择就是设计一种松散耦合的基于服务的系统。
The best choice is to design a loosely coupled system based on services.
SOA促进松散耦合、问题分离、实现封装和标准化合同等设计原则。
SOA promotes design principles like loose coupling, separation of concern, implementation encapsulation, and standardized contracts.
服务操作可以设计成使用单个输入、输出以及出错信息，但是这并不是必要的，并且可能会导致意料之外的标志数据耦合。
Service operations can be designed to use single input, output, and fault messages, but this is not necessary, and can result in undesirable stamp data coupling.
这就是您必须保持代码、内容和显示松散耦合的原因—抛弃糟糕的设计成为减轻痛苦的手段。
That is why you must keep code, content, and presentation loosely coupled — scrapping bad designs becomes a lesser pain.
从设计的角度来看，这是数据模型与视图生成耦合的经典问题。
From a design perspective, this is a classic problem of the data model being coupled to view generation.
通过一个个较小的松散耦合的部件来设计和编写大型应用程序总是更可取的。
It is always preferable to design and code a big application in smaller loosely coupled parts.
这两个职责分配原则在完成良好的面向对象设计的方面扮演了主要角色：高内聚和低耦合。
Two responsibility assignment principles play a major role in achieving good object-oriented design: high cohesion and low coupling.
大型系统的紧密耦合特征通常是通过优化总体设计和尽可能减少系统组件间的冗余和低效情况来实现的。
The tight coupling characteristics of large-scale systems generally result from optimizing the overall design and from minimizing redundancies and inefficiencies among the system's components.
架构上，NWPI在BPM和SOA之间建立了强耦合，因为服务总是被作为业务过程的一部分设计。
Architecturally, NWPI establishes a strong coupling between BPM and SOA as services are always designed to be part of a business process.
耦合和内聚的概念、结构化分析和设计、封装、模式的使用，全都在那儿供我们差遣[5]、[6]、[7]。
The notions of coupling and cohesion, structured analysis and design, encapsulations, the use of patterns, it's all there for the taking [5], [6], [7].
SOA方法允许并提倡使用包括封装、服务组合、松耦合和重用在内的设计原则和模式。
SOA approaches enable and encourage design principles and patterns encompassing encapsulation, service composition, loose coupling, and reuse.
复合应用程序松散耦合的优势之一就是，可在组件创建和设计完成之后再组装应用程序。
One of the great advantages of the loose coupling of composite applications is that application assembly can be conducted much later than component creation and design.
监视系统的代码耦合度量有助于您掌握可破坏架构的常见趋势，即设计刚度、包熵和不必要的依赖性。
Monitoring your system's code coupling metrics will help you stay on top of common trends that can undermine its architecture, namely design rigidity, package entropy, and unwanted dependencies.
为了不把整个结构和所需产品耦合在一起，通常在设计来与外部厂商代码交互的应用中包括进一个抽象层。
So as not to couple the entire architecture to the desired product, it is common to include an abstraction layer in applications designed to interface with outside vendor code.
只有少数的提供者设计时利用了SOA以及它的低耦合和动态本性。
There are only a small number of suppliers, designed to take advantage of SOA and its loosely coupled and dynamic nature.
正像连续地监视传入耦合可以揭示架构设计中的熵一样，监视传出耦合也有助于发现不必要的依赖性。
Just as continuously monitoring afferent coupling can uncover entropy in an architectural design, so monitoring efferent coupling can assist you in spotting unwanted dependencies.
本文讨论的内容也适用于其他遵循“松耦合POJO”设计理念的企业中间件框架。
The topics covered in this article also apply to other lesser-known enterprise middleware frameworks, as they all converge on the "loosely coupled POJO" design.
我们还应该保证，通过合适的SOA技术所获得的成功不能被紧耦合的数据设计所抵消。
We need to ensure that the gains we have made through the use of appropriate SOA technology components are not negated by tightly-coupled data design.
数据：使用文档类型的接口设计来实现松散耦合。
Data: The use of document style interface design to promote loose coupling.
解决这些问题可以帮助完成紧密耦合WebServices的设计、开发和部署工作。
Resolving these issues helps with the jobs of design, development, and deployment of tightly coupled Web services.
我比较赞同ashraf的观点——将OO的设计原则(封装、松耦合、重组合轻继承)应用于SOA。
I find myself agreeing with Ashraf in his advocation of using basic oo design principles (encapsulation, loose coupling, favour composition over inheritance etc) concepts in applying these to SOA.
Web服务背后的概念帮助您使用抽象的接口设计松散耦合的服务，这样就可以把服务实现与服务定义分开。
The concepts behind web services help you design loosely coupled services with abstract interfaces, thus decoupling service implementation from service definition.
应用推荐