与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.
因为对于每个提供程序来说此实现是不同的，所以管理JMS对象或消息提供程序的人员必须了解如何配置实现层。
Because this implementation is different for each provider, those who administer the JMS objects or the messaging provider must understand how to configure the implementation layer.
与传统设计模式不同，此模式更趋向于基础设施层，利用的是消息传递中间件提供的现有功能。
Unlike traditional design patterns, this pattern is more at the infrastructure level and leverages existing capabilities provided by the messaging middleware.
应用推荐