知识卡片
恐怖Saga的逆序恢复难题
Horror Story Saga同时采用异步、整体原子目标和舞蹈:没有中央协调器,却要求多个服务撤销一组可能乱序完成的更新。Alpha未完成又开始Beta,Alpha失败后,参与服务要辨认各自待决事务并按正确依赖逆序撤销。降低了部分耦合并不降低恢复复杂度;整体原子要求与异步、分散协调互相牵制,通常应先重新审视业务是否必须整体原子。
[[异步原子编排增添竞态]]保留协调器;这里还把协调移交给了各服务。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 事务Saga · 查看原书依据
In this pattern, no mediator exists to manage transactional consistency across multiple services—while using asynchronous communication. Thus, each domain service must track undo information about multiple pending transactions, potentially out of order because of asynchronicity, and coordinate with each other during error conditions.
参考来源
- 位置:《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)
- 结论依据:原文的定义、示例或失败路径支持以下归纳:Horror Story Saga同时采用异步、整体原子目标和舞蹈:没有中央协调器,却要求多个服务撤销一组可能乱序完成的更新。 其他条件结合本章同小节说明;不将模式目标当成已有运行保证。
- 原始内容:In this pattern, no mediator exists to manage transactional consistency across multiple services—while using asynchronous communication. Thus, each domain service must track undo information about multiple pending transactions, potentially out of order because of asynchronicity, and coordinate with each other during error conditions.