知识卡片
实例可丢弃依赖退出协议
快速启动有助于及时扩容,优雅关闭则应保存必要数据、关闭连接、完成进行中的工作或把任务交回队列。实例可以替换的前提,是重要状态和工作归属不只存在于它内部。收到停止信号并不保证有无限时间,系统必须明确关闭顺序和可接受的未完成边界。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- It’s All About Dependability · 查看原书依据
Services should also be capable of shutting down when they receive a SIGTERM signal by saving all data that needs to be saved, closing open network connections, or finishing any in-progress work that’s left or by returning the current job to the work queue. X. Development/Production Parity Keep development, staging, and production as similar as
参考来源
- 位置:《Cloud Native Go》第06章《It’s All About Dependability》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch06.xhtml)
- 结论依据:快速启动有助于及时扩容,优雅关闭则应保存必要数据、关闭连接、完成进行中的工作或把任务交回队列。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:Services should also be capable of shutting down when they receive a SIGTERM signal by saving all data that needs to be saved, closing open network connections, or finishing any in-progress work that’s left or by returning the current job to the work queue. X. Development/Production Parity Keep development, staging, and production as similar as