您对松耦合的定义是否太过狭窄呢？
问题是应用松耦合总是有代价的。
The problem is that the application of loose coupling always has a price.
另一个目标是实现组件之间的松耦合。
Another objective was to achieve loose coupling among components.
以关键概念“松耦合”为例。
这种方式不符合SOA的松耦合概念。
This approach does not respect the loose coupling concept of SOA.
对松耦合有许多方面要考虑。
这个报告是这样说明松耦合实现级别的。
The report has this to say about Implementation loose-coupling.
这是因为松耦合并不适于应用设计的所有层级。
This is because loose coupling is not appropriate at all levels of application design.
在客户端组件和它们所使用的服务之间建立了松耦合。
Creates loose couplings between the client components and the services they use.
可将其看作松耦合架构按比例缩小至芯片级。
Think about the loosely-coupled architecture being scaled down to the chip level.
InfoQ：就松耦合和SCA，你们能提供些看法吗？
InfoQ: Could you provide some perspective on loose coupling and SCA?
按照SOA的说法，你应该将松耦合应用在适合它的地方。
According to SOA you should apply loose coupling where it is appropriate.
管理是松耦合问题的关键，而松耦合是服务抽象的核心架构原则。
Management is the key to loose coupling-the core architectural principle behind the service abstraction.
但是，松耦合有很多不同的形式(在我的书中就列举了11种)。
But loose coupling has many different forms (in my book I list 11 of them).
但是，松耦合有很多不同的形式(在我的书中就列举了11种)。
But loose coupling has many different forms (in my book I list 11 of them).
应用推荐