返回主题:基础设施设计流程与模式

知识卡片

普通读书笔记卡 · 3401.a

环境边界必须可演进

理解等级:中级

环境是已部署基础设施的逻辑分组,可以按交付阶段、系统与团队责任,或地区及客户副本划分。这些维度可以交叉。初始设计无法预见未来需求,所以必须考虑上线后如何拆分、合并环境与迁移服务,而非把环境结构视为一次性决定。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 设计环境 · 查看原书依据

      A multi-environment architecture has at least three categories: Providing delivery environments for change management, such as software delivery Splitting environments for manageability, such as ownership by different groups Replicating and customizing environments for separate user bases, such as regions, customers (with dedicated single-tenancy environments), or brands or products More-complex systems often find the need to

    参考来源

    - 位置:《Infrastructure As Code》第12章《设计环境》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch12.html) - 结论依据:原文说明环境是已部署基础设施的逻辑分组,可以按交付阶段、系统与团队责任,或地区及客户副本划分;本卡据此解释其用途及适用边界。 - 原始内容:A multi-environment architecture has at least three categories: Providing delivery environments for change management, such as software delivery Splitting environments for manageability, such as ownership by different groups Replicating and customizing environments for separate user bases, such as regions, customers (with dedicated single-tenancy environments), or brands or products More-complex systems often find the need to