知识卡片

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

大泥球累积变更依赖

理解等级:中级

大泥球指结构混乱且高度耦合的系统,局部变更难以预测地影响其他部分。数仓中的脚本、表、视图与调度互相交织时也可能出现这种现象。绕过规范的快速交付会积累未来返工,不能只按眼前完成速度衡量收益。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • The Journey to Becoming Data-Driven · 查看原书依据

      A big ball of mud is a haphazardly structured, sprawling, sloppy, duct-tape-and-baling-wire, spaghetti-code jungle. The term, introduced by Brian Foote and Joseph Yoder, describes a system architecture that is monolithic, difficult to understand, hard to maintain, and tightly coupled because of its many dependencies. Figure 1-3 shows a dependency diagram that illustrates this. Each line represents a relationship between two software components.

    参考来源

    - 位置:《Data Management at Scale》第01章《The Journey to Becoming Data-Driven》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch01.html) - 结论依据:原文对haphazardly structured的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:A big ball of mud is a haphazardly structured, sprawling, sloppy, duct-tape-and-baling-wire, spaghetti-code jungle. The term, introduced by Brian Foote and Joseph Yoder, describes a system architecture that is monolithic, difficult to understand, hard to maintain, and tightly coupled because of its many dependencies. Figure 1-3 shows a dependency diagram that illustrates this. Each line represents a relationship between two software components.