与api层策略不同，此策略的另一个限制是，您不能“欺骗”并将它增量式地引入到应用程序体系结构中。
Another limitation of this strategy, unlike the API Layer transaction strategy, is that you cannot "cheat" and introduce it into your application architecture incrementally.
正如您所看到的，体系结构概括了关于软件(和硬件)的最重要的决策，并且将它们限制于能够经受住时间考验的决策。
As you can see, architecture summarizes the most important decisions about the software (and hardware) and limits them to those decisions that will stand the test of time.
可以通过两种方式来处理异常情况：架构师可以对新的应用程序的体系结构强加一些限制和约束，使其遵循现有的体系结构构造。
Exceptions can be dealt with in two ways: The architects can impose limitations and constraints on the architecture of the new application so that it follows the existing architectural constructs.
应用推荐