知识卡片
状态修复隔离用户等待
工单已修好但调查服务不可用时,可以把Saga置为NO_SURVEY并向专家返回成功,协调器随后重试;自动恢复失败再交管理员修复。该方法承认“维修完成”和“调查已发”是不同事实,用户不必为后续调查等待或重做维修提交。前提是业务容许这段不一致,而且系统持续跟踪并修复待决状态;不应把提前响应误解为工作流已经全部结束。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 事务Saga · 查看原书依据
However, with this type of saga, rather than issue a compensating update, the state of the saga is changed to NO_SURVEY and a successful response is sent to the Sysops Expert (step 7 in the diagram). The Ticket Orchestrator Service then works asynchronously (behind the scenes) to resolve the error programmatically by retries and error analysis.
参考来源
- 位置:《Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)》第12章《Chapter 12. Transactional Sagas》(来源项目: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/ch12.xhtml)
- 结论依据:原文的定义、示例或失败路径支持以下归纳:工单已修好但调查服务不可用时,可以把Saga置为NO_SURVEY并向专家返回成功,协调器随后重试;自动恢复失败再交管理员修复。 其他条件结合本章同小节说明;不将模式目标当成已有运行保证。
- 原始内容:However, with this type of saga, rather than issue a compensating update, the state of the saga is changed to NO_SURVEY and a successful response is sent to the Sysops Expert (step 7 in the diagram). The Ticket Orchestrator Service then works asynchronously (behind the scenes) to resolve the error programmatically by retries and error analysis.