← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 2275.as.6.f.3.c.1.g.1.a.4

MDM集成需协调时间状态

理解等级:高级

MDM既消费也提供数据,可用批、API和事件满足不同速度。分析主库与消费者若读取不同时间版本,会产生对不上号的状态;宜共享可追踪的产品来源与版本,并为操作路径验证匹配延迟,不能假定任何接入都实时一致。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Modern Master Data Management · 查看原书依据

      For use cases that can tolerate higher latency, you can distribute master data using your data product architecture. However, it’s important to not make point-to-point connections between the MDM hub and providing and consuming applications. If you do this, there’s a risk of data inconsistency. Data consumers, for example, might get new records delivered from the MDM hub directly, while data products aren’t yet up-to-date

    参考来源

    - 位置:《Data Management at Scale》第10章《Modern Master Data Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch10.html) - 结论依据:原文对data products aren’t yet up-to-date的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:For use cases that can tolerate higher latency, you can distribute master data using your data product architecture. However, it’s important to not make point-to-point connections between the MDM hub and providing and consuming applications. If you do this, there’s a risk of data inconsistency. Data consumers, for example, might get new records delivered from the MDM hub directly, while data products aren’t yet up-to-date