在所有实现SOA的途径之中，WOA已经展现出了高度的可共享性与松耦合性。
Of all the approaches to SOA, WOA has demonstrated the high degrees of sharability and loose coupling ...
云应用程序安全性会对特定的特征产生重大影响：多租户、并行性和松耦合性都会增加安全性需求。
Cloud application security impacts certain characteristics strongly: Multi-tenancy, parallelism, and loose coupling introduce additional security needs.
这个实现能力的命名并不妥当，因为它混合了相关的“服务松耦合”原则和“服务可组合性”原则。
This Implementation capability is a bit of a misnomer as it mixes the pertinent “Service Loose Coupling” principle with the “Service posability” principle.
这个列表遗漏了松耦合最重要的一个方面：普遍性。
This list leaves out the most important aspect of loose coupling: ubiquity.
但这听起来像是您已确定松耦合的最重要方面是语言中立性和异步操作。
But it sounds like you have decided that the most important aspects of loose coupling are language neutrality and asynchronous operations.
与此相反，SO范式试图通过松耦合来促进灵活性和敏捷性。
In contrast, the SO paradigm attempts to promote flexibility and agility through loose coupling.
无状态性是松耦合的一种特性，其中服务的每一个调用都不依赖前一个调用。
Statelessness is a property of loose coupling in which every call to a service does not depend on the previous call.
SOA需要高级别的技术优势和设计，因为它要求松耦合、可使用性和抽象。
SOA demands a high level of technical excellence and design because it demands loose coupling, reusability and abstraction.
如果没有考虑如何架构、设计和开发松耦合的服务，那么敏捷性和有效重用的承诺将无法得到满足。
Without investing in thinking through how to architect, design, and build loosely-coupled services, the promises of agility and effective reuse will not be fulfilled.
松耦合和“服务抽象”原则及“服务可重用性”原则一起都是可组合服务的核心驱动力。
Loose coupling together with the "service Abstraction" principle and the "service Reusability" principle are central enablers of composable services.
尽管松耦合的重要性得到认识已经有些时日了，但是围绕这个帖子展开的对话却收集了一些有趣的讨论。
Although the importance of loose-coupling has been known for some time, the dialogue around this post has garnered some interesting discussion.
松耦合和无状态性。
此解决方案框架通过更简单的松耦合方法为IT解决方案提供增强的灵活性和适应性。
This solution framework enables increased agility and adaptability of it solutions through a more simplified loosely-coupled approach.
这样设计的系统具有更大的可伸缩性、灵活性及可复用性，实现了各个层次间的松耦合。
Such a system is flexible, reusable and coupled loosely between the tiers. Then, a Logistics information system is implemented applying the framework.
实现了业务应用单元与工作流管理系统之间的松耦合关系，增强了工作流系统的灵活性和适应性。
Besides, the loose coupled relations between business element and workflow management system are achieved which will also enhance the flexibility and adaptability of the workflow system.
实例研究表明，该方法在并发软件设计阶段实现了横切关注点的分离策略，并使得系统模型具有松耦合、适应性和可跟踪性的优点。
The purview control of the log record and the management of the users are used as the example to study the crosscutting concerns, and the relevant solutions are proposed.
实例研究表明，该方法在并发软件设计阶段实现了横切关注点的分离策略，并使得系统模型具有松耦合、适应性和可跟踪性的优点。
The purview control of the log record and the management of the users are used as the example to study the crosscutting concerns, and the relevant solutions are proposed.
应用推荐