The architecture in Figure 1 implements the Client Orchestration transaction strategy.
图1中的体系结构实现了客户端编排事务策略。
The following rules and characteristics apply to the Client Orchestration transaction strategy.
以下规则和特性适用于客户端编排事务策略。
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 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.
如果您的客户端不支持事务,但您发现客户端编排事务策略非常合适,那么需要执行一些重构。
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层开始,因此这违反了客户端编排事务策略的主要原则。
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层开始,因此这违反了客户端编排事务策略的主要原则。
应用推荐