知识卡片

普通读书笔记卡 · 1841.h.1.a.1.a.3.f.1.g.1.a

迁移复杂度取决于依赖

理解等级:高级

无遗留数据和外部依赖时,结构替换较直接;有历史数据时需要转换;同时有外部消费者时还须维持双版本兼容。原书拆姓名的触发器只说明过渡思路,其条件对更新优先级和冲突处理并不充分,不能直接作为生产双向同步方案。应单独验证旧写、新写、并发与回填路径。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Evolutionary Data · 查看原书依据

      This is the most complex and, unfortunately, most common scenario. Companies need to migrate existing data to new columns while external systems depend on the name column, which the other teams cannot migrate to use the new columns in the desired time frame. The required SQL appears in Example 6-6.

    参考来源

    - 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第06章《Evolutionary Data》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch06.html;段落定位:This is the most complex and, unfortunately, most common scenario) - 结论依据:原文对“迁移复杂度取决于依赖”的定义或案例,支撑“无遗留数据和外部依赖时,结构替换较直接;有历史数据时需要转换;同时有外部消费者时还须维持双版本兼容”的归纳。据其上下文,原书拆姓名的触发器只说明过渡思路,其条件对更新优先级和冲突处理并不充分,不能直接作为生产双向同步方案。 - 原始内容:This is the most complex and, unfortunately, most common scenario. Companies need to migrate existing data to new columns while external systems depend on the name column, which the other teams cannot migrate to use the new columns in the desired time frame. The required SQL appears in Example 6-6.