知识卡片
读副本不拥有写权限
共享数据可以由单一领域拥有写责任,其他服务缓存所需的只读版本,按适当频率更新。写请求回到所有者,由其发布变化。这样避免所有服务直接共享表,但代价是缓存陈旧与同步治理;读副本不能被当作另一个权威写入点。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Evolutionary Data · 查看原书依据
A common approach by many teams is to carefully consider who should own data (i.e., who can update it) versus who can read some version of it. The solution shown in Figure 6-10 uses in-process caching for read access.
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第06章《Evolutionary Data》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch06.html;段落定位:who should own data (i.e., who can update it))
- 结论依据:原文对“读副本不拥有写权限”的定义或案例,支撑“共享数据可以由单一领域拥有写责任,其他服务缓存所需的只读版本,按适当频率更新”的归纳。据其上下文,写请求回到所有者,由其发布变化。
- 原始内容:A common approach by many teams is to carefully consider who should own data (i.e., who can update it) versus who can read some version of it. The solution shown in Figure 6-10 uses in-process caching for read access.