知识卡片
交付保证从最坏出发
事件驱动系统应假定网络慢、服务器故障、重复和乱序会发生:用outbox可靠发布,让订阅者能去重并识别及重排消息,跨上下文补偿则使用saga或流程管理器。选事件类型时再看一致性需求:允许最终一致可用ECST,需读生产者最后写入值则用通知后查询。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 事件驱动架构 · 查看原书依据
Use this as a guiding principle when designing event-driven systems: The network is going to be slow. Servers will fail at the most inconvenient moment. Events will arrive out of order. Events will be duplicated. Most importantly, these events will occur most frequently on weekends and public holidays. The word driven in event-driven architecture means
参考来源
- 位置:《Learning Domain-Driven Design》第15章《事件驱动架构》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch15.html)
- 结论依据:原文列出最坏交付条件及可靠发布、去重、重排和补偿原则,再按一致性选择事件类型。
- 原始内容:Use this as a guiding principle when designing event-driven systems: The network is going to be slow. Servers will fail at the most inconvenient moment. Events will arrive out of order. Events will be duplicated. Most importantly, these events will occur most frequently on weekends and public holidays. The word driven in event-driven architecture means