知识卡片
外置状态转移可靠性责任
把日志放进数据库,可让多个服务副本使用外部状态机制,减少本地文件随实例消失的问题;同时引入网络依赖、容量瓶颈、初始化和运维责任。数据库不能只被视为一个永远可用的黑盒,外置也不自动让各实例内存视图持续同步。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Building a Cloud Native Service · 查看原书依据
externalizing a service’s data into another service designed specifically for that purpose — a database — is a common pattern that allows state to be shared between service replicas and provides data resilience. Besides, the point is to show how we might interact with a database, not to design the perfect application. In this section,
参考来源
- 位置:《Cloud Native Go》第05章《Building a Cloud Native Service》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch05.xhtml)
- 结论依据:把日志放进数据库,可让多个服务副本使用外部状态机制,减少本地文件随实例消失的问题;同时引入网络依赖、容量瓶颈、初始化和运维责任。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:externalizing a service’s data into another service designed specifically for that purpose — a database — is a common pattern that allows state to be shared between service replicas and provides data resilience. Besides, the point is to show how we might interact with a database, not to design the perfect application. In this section,