← 返回起始笔记位置

知识卡片

普通读书笔记卡 · 2275.as.6.f.3.c.9.d.1.b.3

事件转换应留在域边界

理解等级:中级

接收侧和发布侧之间可设置转换组件,将原始事件映射为稳定业务结构,并支持版本兼容。路由与模式可元数据驱动;领域规则仍由生产或消费域负责,公共消息平台不能暗中承包所有业务转换。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Event and Notification Management · 查看原书依据

      To make your architecture more self-service, you could think of a design where routing and mapping are metadata-driven. This could be accomplished, for example, by adding a config store that holds metadata indicating which event streams relate to which other event streams. The functions then will read from this store while processing events. You could even extend this approach by implementing a small control framework

    参考来源

    - 位置:《Data Management at Scale》第06章《Event and Notification Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch06.html) - 结论依据:原文对routing and mapping are metadata-driven的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:To make your architecture more self-service, you could think of a design where routing and mapping are metadata-driven. This could be accomplished, for example, by adding a config store that holds metadata indicating which event streams relate to which other event streams. The functions then will read from this store while processing events. You could even extend this approach by implementing a small control framework