知识卡片

普通读书笔记卡 · 2275.as.6.f.3.c.1.e.2.d.1.c.2

流保留需生命周期控制

理解等级:高级

长期保留可支持副本重建与历史分析,也增加成本、删除与隐私治理负担。可按需求压缩到最新状态或卸载到历史存储。共享企业事件平台若同时成为应用主数据库,会混合治理与故障责任,需明确边界。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Event and Notification Management · 查看原书依据

      When persisting data for longer periods, you should determine under what conditions streams can have long-term or infinite (permanent) data retention. One risk of implementing longer retention periods without monitoring is that your architecture can become costly. You might also violate retention and data life cycle management policies, such as the GDPR. Thus, a form of control is required. One principle you could set is

    参考来源

    - 位置:《Data Management at Scale》第06章《Event and Notification Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch06.html) - 结论依据:原文对long-term or infinite的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:When persisting data for longer periods, you should determine under what conditions streams can have long-term or infinite (permanent) data retention. One risk of implementing longer retention periods without monitoring is that your architecture can become costly. You might also violate retention and data life cycle management policies, such as the GDPR. Thus, a form of control is required. One principle you could set is