知识卡片
管理任务与配置变更分开
数据修复、迁移等有界管理任务可作为短命进程执行;需要永久改变服务或环境时,应修改构建或配置来源,再生成可替换实例。直接登录某台机器临时修改会制造难以重现的“雪花”,使集群和测试环境逐渐偏离。一次任务也需要可追溯输入与结果,不能借此绕过变更管理。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- It’s All About Dependability · 查看原书依据
If your task is an administrative process, like a data repair job or database migration, it should be run as a short-lived process. Containers and functions are excellent vehicles for such purposes. If your change is an update to your service or execution environment, you should instead modify your service or environment construction/configuration scripts, respectively.
参考来源
- 位置:《Cloud Native Go》第06章《It’s All About Dependability》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch06.xhtml)
- 结论依据:数据修复、迁移等有界管理任务可作为短命进程执行;需要永久改变服务或环境时,应修改构建或配置来源,再生成可替换实例。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:If your task is an administrative process, like a data repair job or database migration, it should be run as a short-lived process. Containers and functions are excellent vehicles for such purposes. If your change is an update to your service or execution environment, you should instead modify your service or environment construction/configuration scripts, respectively.