← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 2313.e.5.f.11

微服务边界也是团队边界

理解等级:高级

微服务把能力封装到独立进程并通过API协作,抽象让调用者只关注能力,封装让实现方能在契约内改变细节。这支持独立发布和按各自状态模型扩缩容,却增加跨网络调试及固定部署成本。服务粒度应支撑清楚的所有权,不能只追求拆分数量。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Part III. Serving Patterns · 查看原书依据

      The design of a service architecture is much like the design of a class hierarchy—its goals are to introduce abstraction, encapsulation, and modularity. It is important to note that in each of these categories the “right” design has as much to do with the humans involved in building

    参考来源

    - 位置:《Designing Distributed Systems, 2nd Edition》第part03章《Part III. Serving Patterns》(来源项目 book-sources;源文件:extracted/Designing Distributed Systems, 2nd Edition/_epub-src/OEBPS/part03.html) - 结论依据:引言把抽象、封装、团队边界与微服务收益和过细拆分代价联系。 - 原始内容:The design of a service architecture is much like the design of a class hierarchy—its goals are to introduce abstraction, encapsulation, and modularity. It is important to note that in each of these categories the “right” design has as much to do with the humans involved in building