The answer is to use the High Concurrency transaction strategy.
答案是使用High Concurrency事务策略。
Remember, what I described in this article is a transaction strategy.
记住，本文所描述的是一种事务策略。
Many trade-offs and issues are associated with this transaction strategy.
很多折衷和问题都与这个事务策略相关。
The architecture in Figure 1 implements the API Layer transaction strategy.
图1中的架构实现了APILayer事务策略。
If you do not comply with these rules, the transaction strategy will not work.
如果不遵守这些法则的话，事务策略将不能正常工作。
Be sure to analyze your error rate before selecting this transaction strategy.
确保在选择该事务策略之前分析错误率。
It is the most robust, simplest, and easiest-to-implement transaction strategy.
它是最健壮、最简单并且是最容易实现的事务策略。
The API Layer transaction strategy will work fine for most business applications.
APILayer事务策略将良好地应用于大多数业务应用程序。
Choosing the right transaction strategy is critical for your application's success.
选择正确的事务策略对应用程序的成功至关重要。
The implementation of the API Layer transaction strategy is fairly straightforward.
APILayer事务策略的实现相当简单。
The following rules and characteristics apply to the API Layer transaction strategy.
以下规则和特征将应用到APILayer事务策略。
Let me explain why this is so important (and necessary) for this transaction strategy.
让我解释一下它对事务策略的重要性(和必要性)。
The architecture in Figure 1 implements the Client Orchestration transaction strategy.
图1中的体系结构实现了客户端编排事务策略。
That makes this transaction strategy ill suited for applications that are "chatty."
这使得这种策略不太适合“聊天”应用程序。
Many risks are associated with this transaction strategy, and it is complex to implement.
这个事务策略伴随着很多风险，并且实现起来也很复杂。
A significant amount of design effort goes into developing an overall transaction strategy.
开发一个完整的事务策略涉及大量的设计工作。
In "The API Layer strategy," I outlined two golden rules for building a transaction strategy.
在“api层策略”中，我概述了构建事务策略的两条黄金法则。
This transaction strategy is well-suited for applications that have a coarse-grained API layer.
这个事务策略非常适合拥有粗粒度api层的应用程序。
The following rules and characteristics apply to the Client Orchestration transaction strategy.
以下规则和特性适用于客户端编排事务策略。
None of that matters with respect to how the transaction strategy works or how it is implemented.
这都不会影响事务策略的工作方式或实现方式。
In some cases, you may need to refactor your application logic to support this transaction strategy.
在某些情况下，您可能需要重构应用程序逻辑，以支持这种事务策略。
I mention these rules again because they also apply to the Client Orchestration transaction strategy.
我再次提到了这些规则，因为它们同样适用于客户端编排事务策略。
This transaction strategy is well-suited for applications that have a complex and fine-grained API layer.
这种事务策略非常适合拥有复杂和细粒度api层的应用程序。
This causes the transaction to complete (commit or roll back) faster than in the API Layer transaction strategy.
其结果是，事务会比在api层事务策略中更快地完成(提交或回滚)。
As you can see from this overview, developing an effective transaction strategy is not always a straightforward task.
从这篇概述中可以看到，开发一个有效的事务策略并非总是一项简单的任务。
In some circumstances you might need to trade some level of performance for a slower ACID-based transaction strategy.
在某些情况下，您可能需要牺牲一些性能，使用较慢的基于ACID的事务策略。
To illustrate the read-first technique, I'll start with some code that implements the API Layer transaction strategy.
为了演示这种先读取技巧，我们从一些实现api层事务策略的代码入手。
It is also perhaps the most difficult and cumbersome transaction strategy to implement out of the four introduced here.
它可能是这四个事务策略中最难以实现的一个。
I typically ask the architect or technical lead in a client engagement to describe their project's transaction strategy.
我经常会让与客户接触的架构师和技术总监描述他们项目的事务策略。
In these circumstances, you would use the High Concurrency transaction strategy - the topic of this series' fifth article.
遇到这种情况，需要使用High Concurrency事务策略—本系列第5篇文章的主题。
应用推荐