The architecture in Figure 1 implements the Client Orchestration transaction strategy.
图1中的体系结构实现了客户端编排事务策略。
The following rules and characteristics apply to the Client Orchestration transaction strategy.
以下规则和特性适用于客户端编排事务策略。
This transaction attribute is used in the Client Orchestration transaction strategy described in this article's next section.
这个事务属性应用于本文下一部分将要讨论的Client Orchestration事务策略。
In this article, I'll describe the Client Orchestration transaction strategy, which I introduced briefly in "Models and strategies overview."
在本文中，我将讨论客户端编排事务策略，而我之前在“模型和策略概述”一文中简要介绍了这方面的内容。
The Client Orchestration transaction strategy is used when multiple server-based or model-based calls from the client layer fulfill a single unit of work.
当来自客户机层的基于多服务器或基于模型的调用完成单一工作单元时，将使用Client Orchestration事务策略。
This strategy is difficult to implement, takes longer to develop and test, and is more error prone than the API Layer or Client Orchestration strategies.
此策略难以实现，并且需要更长的时间进行开发和测试，并且比api层或ClientOr chestration策略更易于出错。
The client Orchestration transaction strategy is useful when most of the requests from the client layer require multiple calls to the API layer to complete a single LUW.
当来自客户端层的大多数请求都需要向api层发起多个调用才能完成一个LUW时，客户端编排事务策略将非常有用。
Don't be tempted to mix the Client Orchestration strategy and API Layer strategy in the same application to try to solve every permutation in your application architecture.
不要尝试在相同应用程序中混合客户端编排策略和api层策略，以期解决应用程序体系结构中的所有变化。
If you do have clients that do not support transactions but you find the client Orchestration transaction strategy seems like a good fit, you may have to do some refactoring.
如果您的客户端不支持事务，但您发现客户端编排事务策略非常合适，那么需要执行一些重构。
The API Layer and Client Orchestration transaction strategies that I've covered in previous articles in this series are core strategies that apply to most standard business applications.
我在本系列的前几篇文章中所介绍的api层和客户端编排策略事务策略是应用于大多数标准业务应用程序的核心策略。
Furthermore, using REQUIRED in the API layer methods means that a transaction could be started by the API layer, thereby violating the main principles of the Client Orchestration transaction strategy.
此外，在api层方法中使用REQUIRED意味着事务可以由api层开始，因此这违反了客户端编排事务策略的主要原则。
In this option, a fifth component, called the Controller, is added for performing interaction orchestration between the four core components and to provide user interface with an external client.
在这个选项中，添加了第5个组件Controller来执行4个核心组件之间的协调，同时为用户接口提供一个外部客户端。
The [main] client app’s challenges are aggregation, parallelization, and orchestration of forks and joins.
客户端的主要挑战是对发起请求（fork）和合并响应（join）的聚合、并行处理和编排。
The [main] client app’s challenges are aggregation, parallelization, and orchestration of forks and joins.
客户端的主要挑战是对发起请求（fork）和合并响应（join）的聚合、并行处理和编排。
应用推荐