知识卡片
事件一致性仍需失败出口
拥有者提交并发布事件,其他服务异步订阅处理,用户不必等全部同步完成。持久订阅或持久事件保留帮助暂时不可用的消费者追赶;持续处理失败则可能重试后进入死信队列,需自动修复或人工处理。较快响应和时间上较快收敛不能替代处理成功保证,模式仍需设计错误路径。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 数据所有权与分布式事务 · 查看原书依据
Most message brokers will try a certain number of times to deliver a message, and after repeated failures by the receiver, the broker will send the message to a dead letter queue (DLQ). This is a configurable destination where the event is stored until an automated process reads the message and tries to fix the problem. If it can’t be repaired programmatically, the message is then typically sent to a human for manual processing.
参考来源
- 位置:《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)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:Most message brokers will try a certain number of times to deliver a message, and after repeated failures by the receiver, the broker will send the message to a dead letter queue (DLQ). This is a configurable destination where the event is stored until an automated process reads the message and tries to fix the problem. If it can’t be repaired programmatically, the message is then typically sent to a human for manual processing.