高性能是否比松散耦合更为重要？
您对松耦合的定义是否太过狭窄呢？
代码中的耦合也可以变得更松散。
问题是应用松耦合总是有代价的。
The problem is that the application of loose coupling always has a price.
好习惯：在对象之间松散耦合。
另一个目标是实现组件之间的松耦合。
Another objective was to achieve loose coupling among components.
传入耦合比较难判断，但是更有价值。
Afferent coupling is harder to determine and much more valuable.
以关键概念“松耦合”为例。
这种方式不符合SOA的松耦合概念。
This approach does not respect the loose coupling concept of SOA.
对松耦合有许多方面要考虑。
选择将导致最小、最少耦合软件的设计。
Choose designs that will result in the smallest, least coupled software.
并且应用程序之间也存在非常紧密的耦合。
本文中的示例代码与数据库结构紧密耦合。
The example code in this article is strongly coupled to the database structure.
首先，这个改变减少了应用程序的耦合性。
To start with, the change has reduced coupling in the application.
因此，可以将其看作紧密耦合的管理系统。
Hence, it can be thought of as a tightly-coupled management system.
具有高内聚力的设计将提供降低耦合的机会。
Designs with high cohesion offer the opportunity for lower coupling.
松散耦合有许多优点。
最基本的想法就是高度耦合的类要合在一块。
The basic idea is that highly coupled classes belong together.
这是保持耦合松散的一个OSGi最佳实践。
可将其看作松耦合架构按比例缩小至芯片级。
Think about the loosely-coupled architecture being scaled down to the chip level.
这是很简单的，但也是高度耦合的。
This is pretty straightforward, but it's also highly coupled to its environment.
如果要帮助实现松散耦合，请考虑下列事项。
这是因为松耦合并不适于应用设计的所有层级。
This is because loose coupling is not appropriate at all levels of application design.
在软件开发中，某种程度的耦合是不可避免的。
Some level of coupling is inevitable in software development.
SOA的一个关键目标就是组件间的松散耦合。
A key objective of SOA is loose coupling between components.
您还可以利用类长度、方法长度和内部类耦合。
You can also look out for class length, method length, and intra-class coupling.
它是SCA系统内的松散耦合组合的基本单元。
It is the basic unit of loosely-coupled composition within a SCA System.
用户会话与应用程序中的用户会话状态的耦合。
Coupling of user session with user session state in the application.
紧密耦合与松散耦合的对比。
是否要冒“耦合”的风险的决策要您自己来决定。
The decision of whether to take the risk of "coupling" is yours to make.
应用推荐