← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1971.o.1.b.1.a.2.c.1.a.1

跨上下文翻译先看模型差异

理解等级:高级

跨系统集成时,字段格式转换只是机械层。更根本的是两边可能对同一术语、概念和规则有不同理解;同一代码库内不同团队,甚至单个团队的旧代码,也会出现这种分歧。

因此在跨 Bounded Context 传递数据前,应先对照两侧模型语义,明确需要哪些翻译与约束,再做格式映射。若只见字段能对上,就直接复用对象,可能把矛盾带进运行系统。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 原书第14章|Bounded Context · 查看原书依据

      Everyone is aware that the data format of another system is different and calls for a data conversion, but this is only the mechanical dimension of the problem. More fundamental is the difference in the models implicit in the two systems. When the discrepancy is not with an external system, but within the same code base, it is even less likely to be recognized. Yet this happens on all large team projects.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第100章《Bounded Context》(源文件:_epub-src/0321125215_ch14lev1sec1_split_000.html;单元01) - 结论依据:原文指出数据格式转换只是机械问题,模型内含差异更根本;同一代码库和单个团队也可能存在多个模型。 - 原始内容:Everyone is aware that the data format of another system is different and calls for a data conversion, but this is only the mechanical dimension of the problem. More fundamental is the difference in the models implicit in the two systems. When the discrepancy is not with an external system, but within the same code base, it is even less likely to be recognized. Yet this happens on all large team projects.