← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 3302

组织沟通结构塑造API边界

理解等级:高级

系统接口往往映照团队间的沟通路径。设计跨团队 API 时,既要看技术职责,也要看谁拥有契约、如何协商变更和承担运维;若组织边界与服务边界冲突,额外协调成本会持续出现。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • · 查看原书依据

      Or, put more succinctly, “if you have four groups working on a compiler, you’ll get a 4-pass compiler.” We have definitely seen this in the API world—as we like to joke, “if you have four groups working on a microservice system, you’ll get four layers of APIs.” We couldn’t hope to cover the topic of organizational design in the depth it deserves in this book,

    参考来源

    - 位置:《Mastering API Architecture》第10章《Wrap-up》之《APIs, Conway’s Law, and Your Organization》(源文件:_epub-src/OEBPS/ch10.xhtml) - 结论依据:原文引 Conway 定律,并明确 API 系统兼具社会与技术属性。 - 原始内容:Or, put more succinctly, “if you have four groups working on a compiler, you’ll get a 4-pass compiler.” We have definitely seen this in the API world—as we like to joke, “if you have four groups working on a microservice system, you’ll get four layers of APIs.” We couldn’t hope to cover the topic of organizational design in the depth it deserves in this book,