知识卡片
仓库团队替代过细服务
服务细到一人兼职就能维护时,逐服务隔离可能增加更多通信成本。可由一个小团队拥有一个仓库及独立流水线,仓库内允许多个服务共享数据库,团队之间仍保持松耦合。团队成长后再拆仓库、发布边界和数据责任。这把独立交付原则施加在团队负责的单元上,而不机械施加到每个微小进程;需为未来拆分留余地,但避免过早昂贵隔离。
这是把[[微服务为团队独立交付服务]]的目标应用到仓库团队边界。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 宏观架构中的微服务决策 · 查看原书依据
The system is developed by two-pizza teams of programmers, where each team owns a repository. We apply microservices’ principles as if the code in the repository is a microservice. The code can be one service or maybe several, based on its complexity.
参考来源
- 位置:《Software Architecture and Decision-Making》第10章《Macro Architecture: Microservices Considerations》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch10.xhtml)
- 结论依据:摘录说明服务细到一人兼职就能维护时,逐服务隔离可能增加更多通信成本。其余条件结合本章相邻例子与取舍说明,数字示例不作当前性能承诺。
- 原始内容:The system is developed by two-pizza teams of programmers, where each team owns a repository. We apply microservices’ principles as if the code in the repository is a microservice. The code can be one service or maybe several, based on its complexity.