知识卡片
微服务独立发布有前提
微服务通过服务接口消息协作,避免直接共享实现和他人数据,并保持可独立部署的职责边界,可减少跨队技术版本协调。收益以网络、发现、分布式事务、技术栈维护和整体认知成本交换。服务很小并不足够,版本交互、粒度和数据访问仍须有意设计。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 可部署性 · 查看原书依据
The microservice architecture pattern structures the system as a collection of independently deployable services that communicate only via messages through service interfaces. There is no other form of interprocess communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第5章《可部署性》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch05.html)
- 结论依据:原文的定义、机制或比较支持“微服务通过服务接口消息协作,避免直接共享实现和他人数据,并保持可独立部署的职责边界,可减少跨队技术版本协调”;正文保留其条件与取舍。
- 原始内容:The microservice architecture pattern structures the system as a collection of independently deployable services that communicate only via messages through service interfaces. There is no other form of interprocess communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever.