知识卡片

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

共享数据库冻结结构

理解等级:高级

多个应用直接共享模式时,一个应用的结构变化可能破坏其他应用,数据表因此变成跨团队公共接口。它便于初期集成,却容易让后续演进冻结。需要先找到依赖者及契约,再安排迁移,不能只从本应用是否通过测试判断安全。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Evolutionary Data · 查看原书依据

      In Figure 6-1, the three applications share the same relational database. Projects frequently default to this integration style—​every project is using the same relational database because of governance, so why not share data across projects? Architects quickly discover, however, that using the database as an integration point fossilizes the database schema across all sharing projects.

    参考来源

    - 位置:《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;段落定位:Architects quickly discover, however, that using the database) - 结论依据:原文对“共享数据库冻结结构”的定义或案例,支撑“多个应用直接共享模式时,一个应用的结构变化可能破坏其他应用,数据表因此变成跨团队公共接口”的归纳。据其上下文,它便于初期集成,却容易让后续演进冻结。 - 原始内容:In Figure 6-1, the three applications share the same relational database. Projects frequently default to this integration style—​every project is using the same relational database because of governance, so why not share data across projects? Architects quickly discover, however, that using the database as an integration point fossilizes the database schema across all sharing projects.