知识卡片
架构轴看独立变化
架构轴从试错形成的无规则结构,到紧耦合模块、客户端服务端,再讨论独立服务与函数。真正值得观察的是接口、部署和扩展能否独立;“服务超过十个”或“一个服务一个仓库”只是书中例子,不能作为架构资格线。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter 5. Knowing Thyself: The Cloud Native Maturity Matrix Tool · 查看原书依据
Microservices architecture is highly distributed. It comprises a large number (usually more than 10) of independent services that communicate only via well-defined, versioned APIs. Often, each microservice is developed and maintained by one team. Each microservice can be deployed independently, and each has a separate code repository. Hence, each microservice team can work and deploy in a highly parallel fashion, using their own preferred languages and operational tools and datastores
参考来源
- 位置:《Cloud Native Transformation》第05章《Knowing Thyself: The Cloud Native Maturity Matrix Tool》(来源项目a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Cloud Native Transformation/_epub-src/OEBPS/ch05.xhtml)
- 结论依据:原文对本卡对象的定义、区别或前后条件给出直接解释,支持本卡的核心论点:架构轴从试错形成的无规则结构,到紧耦合模块、客户端服务端,再讨论独立服务与函数。本卡进一步说明用途及适用边界;原文过强的保证另在正文限界。
- 原始内容:Microservices architecture is highly distributed. It comprises a large number (usually more than 10) of independent services that communicate only via well-defined, versioned APIs. Often, each microservice is developed and maintained by one team. Each microservice can be deployed independently, and each has a separate code repository. Hence, each microservice team can work and deploy in a highly parallel fashion, using their own preferred languages and operational tools and datastores