知识卡片
云账号隔离粒度需匹配责任边界
一服务一账号提供强隔离和明确成本归属,但需要大量账号及跨账号自动化;按领域分账号降低管理量但增加资源误影响风险。以团队责任、数据边界和运营能力选择粒度。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第8章《Embracing New Technology》(源文件:`_epub-src/OPS/ch08.xhtml`,归一化正文 [12582:16791))
- 结论依据:原文比较一服务一账号、按业务领域共享账号与单账号三种隔离形式。
- 原始内容:One account per service Cloud makes it easy to achieve isolation: you have no reason to share databases across services in production, and the best companies are isolating EVERYTHING they can using all the tools at their disposal, especially accounts: Do not share managed service clusters: Make sure every service has its own, isolated and dedicated cluster. Do not share Aurora MySQL clusters, for instance.