知识卡片

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

历史迁移需单独补缺

理解等级:高级

新架构只从上线时开始积累历史时,可从旧仓库提取必要历史并以遗留产品受控发布,再与新交付衔接。需要核对字段、粒度、重复和语义变化,不能把复制旧文件等同于完成历史一致性。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Putting Theory into Practice · 查看原书依据

      While onboarding new use cases and domains into your architecture, it’s likely that you will run into migration or legacy scenarios. For example, you may encounter situations in which consumers demand historical data from several years back. When building up your new data product architecture, you’ll learn that historical data is only available from the moment you onboarded your first data products into the new

    参考来源

    - 位置:《Data Management at Scale》第12章《Putting Theory into Practice》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch12.html) - 结论依据:原文对historical data is only available的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:While onboarding new use cases and domains into your architecture, it’s likely that you will run into migration or legacy scenarios. For example, you may encounter situations in which consumers demand historical data from several years back. When building up your new data product architecture, you’ll learn that historical data is only available from the moment you onboarded your first data products into the new