← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 4545.d.2

服务拆分交换部署与协调成本

理解等级:高级

单体适合较简单应用及较直接的本地调用,但局部改动通常需整体发布,局部热点也常按整套复制。微服务让功能独立构建、部署和扩展,并增加网络失败、状态协作与运维要求。选择取决于边界、团队和规模;原书“未见成功拆单体”的个人经历不能当作迁移不可能的证据。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Scalability · 查看原书依据

      The defining characteristic of a microservices architecture is a service whose functional components have been divided into a set of discrete sub-services that can be independently built, tested, deployed, and scaled. This is illustrated in Figure 7-4, in which a user interface service — perhaps an HTML-serving web application or a public API — interacts

    参考来源

    - 位置:《Cloud Native Go》第07章《Scalability》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch07.xhtml) - 结论依据:单体适合较简单应用及较直接的本地调用,但局部改动通常需整体发布,局部热点也常按整套复制。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。 - 原始内容:The defining characteristic of a microservices architecture is a service whose functional components have been divided into a set of discrete sub-services that can be independently built, tested, deployed, and scaled. This is illustrated in Figure 7-4, in which a user interface service — perhaps an HTML-serving web application or a public API — interacts