知识卡片

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

内部流与业务流隔离

理解等级:中级

内部流服务域内技术协作,可保留实现细节;跨域业务流需要读友好、稳定、所有者和更完整的登记。可用独立服务、命名、访问控制或集群隔离。其他域不应直接订阅内部流,否则生产者失去独立演化空间。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

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

      Events used for internal communication (such as between two application components) are allowed to be technical; they don’t have to be adapted (yet) for business use. The streams for these events are called internal streams and are considered part of the application or domain logic. This means they can be consumed only by the producing application domain, and aren’t directly consumed by other domains, although

    参考来源

    - 位置:《Data Management at Scale》第06章《Event and Notification Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch06.html) - 结论依据:原文对internal streams的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:Events used for internal communication (such as between two application components) are allowed to be technical; they don’t have to be adapted (yet) for business use. The streams for these events are called internal streams and are considered part of the application or domain logic. This means they can be consumed only by the producing application domain, and aren’t directly consumed by other domains, although