知识卡片

普通读书笔记卡 · 3327.v.1.a

战术分叉留下结构债

理解等级:高级

战术分叉的收益是前期分析少、删除比提取容易;代价是残留潜伏代码、原有混乱结构,以及多副本共享代码难以一致维护。它缩小了代码量,却不自动改善内部设计。维护性和共享功能一致性是主要问题时,已有清晰组件边界往往支持更慢但可控的组件分解。

相关:[[战术分叉以删除代提取]]。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 选择架构分解方法 · 查看原书依据

      Shortcomings The resulting services will likely still contain a large amount of mostly latent code left over from the monolith. Unless developers undertake additional efforts, the code inside the newly derived services won’t be better than the chaotic code from the monolith—there’s just less of it. Inconsistencies may occur between the naming of shared code and shared component files, resulting in difficultly identifying common code and keeping it consistent.

    参考来源

    - 位置:《Software Architecture: The Hard Parts》第4章《选择架构分解方法》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch04.xhtml) - 结论依据:原文的定义、比较或案例支持“战术分叉的收益是前期分析少、删除比提取容易;代价是残留潜伏代码、原有混乱结构,以及多副本共享代码难以一致维护”;正文据此解释其用途与适用边界。 - 原始内容:Shortcomings The resulting services will likely still contain a large amount of mostly latent code left over from the monolith. Unless developers undertake additional efforts, the code inside the newly derived services won’t be better than the chaotic code from the monolith—there’s just less of it. Inconsistencies may occur between the naming of shared code and shared component files, resulting in difficultly identifying common code and keeping it consistent.