知识卡片

普通读书笔记卡 · 3354

隔离限制变更波及面

理解等级:中级

隔离是让组件有各自边界,减少共享状态和隐含副作用,使一个组件的变更或故障较少牵连其他组件。它有程度之分,进程、事务和模块边界都能提供不同形式的隔离;选择边界时要比较独立性收益与协作成本。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    原书出处

    参考来源

    - 位置:《Principles of Software Architecture Modernization》第2章《Anti-Patterns: Lack of Isolation》(源文件:`_epub-src/OPS/ch02.xhtml`,归一化正文 [4140:8328)) - 结论依据:原文将隔离定义为约束变化影响范围、减少全局状态和副作用,并说明隔离是连续谱而非有无二选一。 - 原始内容:Isolation is a way to reduce the blast radius and constrain the potential impact of change. Isolation helps you avoid global impact, global state, and global side effects. After all, do you want to change 1 line of code and impact all classes in the codebase? Isolation is a way to make the code more independent, precise, reliable, scalable, and safe to work with. Isolation is a highly desirable property, and isolation is always a good idea.