知识卡片
请求编排等待整体完成
专用编排器负责参与者、顺序、并行调用和错误处理,等所有服务回应后才答复用户。可以先做最可能阻止流程的步骤,减少后续补偿。它比让某业务服务兼任编排器职责更清楚,但增加跳数与等待,也没有数据库级回滚:局部失败后必须决定重试、补偿或人工修复。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 数据所有权与分布式事务 · 查看原书依据
The approach we generally prefer when using the orchestrated request-based pattern is to use a dedicated orchestration service for the business request. This approach, illustrated in Figure 9-18, frees up the Customer Profile Service from the responsibility of managing the distributed transaction and places that responsibility on a separate orchestration service.
参考来源
- 位置:《Software Architecture: The Hard Parts》第09章《数据所有权与分布式事务》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch09.xhtml)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:The approach we generally prefer when using the orchestrated request-based pattern is to use a dedicated orchestration service for the business request. This approach, illustrated in Figure 9-18, frees up the Customer Profile Service from the responsibility of managing the distributed transaction and places that responsibility on a separate orchestration service.