← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 4378.a.6.a

边车准入看普及率与开销

理解等级:高级

共享基础设施团队维护边车有利于一致性,但不应把所有共享库塞进去。只有少数团队需要的JSON到XML工具会让每个服务承担多余体积;领域类放入边车还会让模型变化强迫多团队协调。应比较真正使用的团队数量与每个实例承担的资源、版本成本,按现实规模决定准入,案例中少于一半不是普适数值定律。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 复用模式 · 查看原书依据

      That’s the key trade-off for shared utility code—how many teams need it versus how much overhead does it add to every service, particularly ones that don’t need it.” “And if less than one-half the teams use it, it’s probably not worth the overhead,” Sydney said.

    参考来源

    - 位置:《Software Architecture: The Hard Parts》第08章《复用模式》(来源项目: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/ch08.xhtml) - 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。 - 原始内容:That’s the key trade-off for shared utility code—how many teams need it versus how much overhead does it add to every service, particularly ones that don’t need it.” “And if less than one-half the teams use it, it’s probably not worth the overhead,” Sydney said.