← 返回起始笔记位置

知识卡片

普通读书笔记卡 · 1971.o.1.b.4.d.1.c.4.a.3.a.7.a.1

外部维度映射能力限定集成边界

理解等级:中级

原书的分配检查器只能处理能转成 Enterprise Segment 的销售维度;若外部系统新增无法映射的维度,这个集成设计就不能直接接受它。把翻译集中在 Allocation Checker 后,销售模型变化主要止于该边界,Cargo Repository 只需理解领域细分。上线前应列出可映射维度及未知值处置;这一步是据原书约束提出的应用检查,非原书已执行的验证结果。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 原书第07章|Introducing a New Feature: Allocation Checking · 查看原书依据

      The only serious constraint imposed by this integration will be that the Sales Management System mustn't use dimensions that the Allocation Checker can't turn into Enterprise Segments. (Without applying the ENTERPRISE SEGMENT pattern, the same constraint would force the sales system to use only dimensions that can be used in a query to the Cargo Repository. This approach is feasible, but the sales system spills into other parts of the domain.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第59章《原书第07章|Introducing a New Feature: Allocation Checking》(源文件:_epub-src/0321125215_ch07lev1sec11.html) - 结论依据:原文把销售系统维度可转化为 Enterprise Segment 设为主要约束,并说明变更影响被检查器吸收。 - 原始内容:The only serious constraint imposed by this integration will be that the Sales Management System mustn't use dimensions that the Allocation Checker can't turn into Enterprise Segments . (Without applying the ENTERPRISE SEGMENT pattern, the same constraint would force the sales system to use only dimensions that can be used in a query to the Cargo Repository . This approach is feasible, but the sales system spills into other parts of the domain.