知识卡片
事件驱动与溯源分工
事件驱动架构以异步事件消息集成服务,属于边界之间的通信设计;事件溯源以事件序列保存状态变化,属于服务内部的建模与持久化设计。内部事件为表达聚合生命周期而存在,不能仅因已经有事件,就自动把它们全部作为跨上下文接口。两者可组合,但各自需要独立设计。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 事件驱动架构 · 查看原书依据
Although both event-driven architecture and event sourcing are based on events, the two patterns are conceptually different. EDA refers to the communication between services, while event sourcing happens inside a service. The events designed for event sourcing represent state transitions (of aggregates in an event-sourced domain model) implemented in the service. They are aimed at
参考来源
- 位置:《Learning Domain-Driven Design》第15章《事件驱动架构》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch15.html)
- 结论依据:原文明确区分服务间通信与服务内状态迁移事件。
- 原始内容:Although both event-driven architecture and event sourcing are based on events, the two patterns are conceptually different. EDA refers to the communication between services, while event sourcing happens inside a service. The events designed for event sourcing represent state transitions (of aggregates in an event-sourced domain model) implemented in the service. They are aimed at