知识卡片
全局规则区分局部需求
企业可统一安全等必须普遍保护的约束,同时让服务团队为可用性和伸缩性等需求选择目标。把所有页面一律要求五个九可能造成过度工程。共享模板应支持分层责任,不能把规则数量或统一程度当作治理质量。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Putting Evolutionary Architecture into Practice · 查看原书依据
To solve these problems, the enterprise architects defined their criteria as fitness functions and created a deployment pipeline template for each project to start with. Within the deployment pipeline, the architects designed fitness functions to automatically check critical features such as security, leaving individual teams to add specific fitness functions (like availability) for their service.
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第09章《Putting Evolutionary Architecture into Practice》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch09.html;段落定位:leaving individual teams to add specific fitness functions)
- 结论依据:原文对“全局规则区分局部需求”的定义或案例,支撑“企业可统一安全等必须普遍保护的约束,同时让服务团队为可用性和伸缩性等需求选择目标”的归纳。据其上下文,把所有页面一律要求五个九可能造成过度工程。
- 原始内容:To solve these problems, the enterprise architects defined their criteria as fitness functions and created a deployment pipeline template for each project to start with. Within the deployment pipeline, the architects designed fitness functions to automatically check critical features such as security, leaving individual teams to add specific fitness functions (like availability) for their service.