知识卡片
退订局部提交留下残态
客户退订时,档案与合同服务已各自提交删除或退订状态,但账单服务更新失败,业务请求因此只完成一部分。调用是同步的也不能撤回其他服务已提交的数据;若补偿再失败,状态进一步失配。本例明确的是客户、合同和账单状态不一致,原文并未证明实际发生重复扣费。对应处理见[[退订补偿需要恢复信息]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 数据所有权与分布式事务 · 查看原书依据
consider what happens when the customer is removed from the Profile table and Contract table, but an error occurs when trying to remove the billing information from the Billing table, as illustrated in Figure 9-19. Since the Profile and Support Contract Services individually committed their operations, the Unsubscribe Orchestrator Service must now decide what action to take while the customer is waiting for the request to be processed: Should the orchestrator send the request again to the Billing Payment Service for another try?
参考来源
- 位置:《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)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:consider what happens when the customer is removed from the Profile table and Contract table, but an error occurs when trying to remove the billing information from the Billing table, as illustrated in Figure 9-19. Since the Profile and Support Contract Services individually committed their operations, the Unsubscribe Orchestrator Service must now decide what action to take while the customer is waiting for the request to be processed: Should the orchestrator send the request again to the Billing Payment Service for another try?