知识卡片
预留自治而不早付成本
Starling早期构建可独立部署的服务,却为小团队方便同步发布,试图保留未来拆分组织的选择。这样能降低初期复杂度,但未练习的独立能力可能衰退;需要持续验证接口和部署独立性,而不能只凭设计图认定保留成功。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter 14. Building a Bank in a Year: Starling Bank Case Study · 查看原书依据
Our approach to capture the benefits of both was to follow a sort of microservices, or maybe miniservices, architecture but to behave monolithically in many ways. For instance, even though we have something like 30 microservices, we tend to release them all at the same time rather than having separate release cycles for all of them. That will change over time, but we’re still working this way almost three years
参考来源
- 位置:《Cloud Native Transformation》第14章《Building a Bank in a Year: Starling Bank Case Study》(来源项目a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Cloud Native Transformation/_epub-src/OEBPS/ch14.xhtml)
- 结论依据:原文以实际公司回顾中的取舍、机制或故障过程提供案例证据,支持本卡的核心论点:Starling早期构建可独立部署的服务,却为小团队方便同步发布,试图保留未来拆分组织的选择。本卡进一步说明用途及适用边界;原文过强的保证另在正文限界。
- 原始内容:Our approach to capture the benefits of both was to follow a sort of microservices, or maybe miniservices, architecture but to behave monolithically in many ways. For instance, even though we have something like 30 microservices, we tend to release them all at the same time rather than having separate release cycles for all of them. That will change over time, but we’re still working this way almost three years