Another limitation of this strategy, unlike the API Layer transaction strategy, is that you cannot "cheat" and introduce it into your application architecture incrementally.
与api层策略不同,此策略的另一个限制是,您不能“欺骗”并将它增量式地引入到应用程序体系结构中。
If your answer is that it is common, you run a greater risk of stale data exceptions, making this strategy a poor choice for your application profile.
如果您的回答是常见,则面临着极高的失效数据异常风险,那么这个策略对于您的应用程序探查来说是一个很差的选择。
The encoding strategy, on the other hand, does not have the above-described maintenance effort, and it also has less impact on the existing application code as well as on application functionality.
相反,编码策略不需要进行上述维护工作,而且它对现有应用程序代码以及应用程序功能的影响也较小。
应用推荐