知识卡片

普通读书笔记卡 · 1980.z.6.b.3

Saga结果与监控边界

理解等级:中级

协同Saga成功结果可能出自最后一个服务,失败结果则出自回滚终点的起始服务,因此只订阅其中一条流无法获得完整终态,更无法看到卡住过程。不能让多个服务为了统一结果而随意写同一流。编排器可作为单一结果生产者,发布进行中与终态实体,同时维护补偿确认、重试和告警。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Building Workflows with Microservices · 查看原书依据

      Suppose now that service C is unable to complete its part of the transaction. It must now reverse the workflow, either by issuing events or by responding to the previous service’s request. Services B and A must revert their portion of the transaction, in order, as shown in Figure 8-6.

    参考来源

    - 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第08章《Building Workflows with Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch08.xhtml;规范化段落起句:Suppose now that service C is unable) - 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:协同Saga成功结果可能出自最后一个服务,失败结果则出自回滚终点的起始服务,因此只订阅其中一条流无法获得完整终态,更无法看到卡住过程。本卡同时保留其适用条件与失败边界。 - 原始内容:Suppose now that service C is unable to complete its part of the transaction. It must now reverse the workflow, either by issuing events or by responding to the previous service’s request. Services B and A must revert their portion of the transaction, in order, as shown in Figure 8-6.