知识卡片

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

交换模式按需求组合

理解等级:高级

批、API和事件可以在摄取与消费两侧组合。选择先看可接受延迟、完整性核对和由谁发起交换,再评估成本、恢复和维护。实时摄取可以供批量产品消费,API也可读最终一致副本,不能单凭工具名称判断业务保证。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Connecting the Dots · 查看原书依据

      When considering data distribution patterns for your use cases, there are two issues to consider. First, you should evaluate the acceptable delay between making operational changes and having them reflected in reads. For example, an application that needs end-of-day data has different requirements than an application that requires data to be delivered within a one-minute time window. Second, you should evaluate the need for periodic

    参考来源

    - 位置:《Data Management at Scale》第07章《Connecting the Dots》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch07.html) - 结论依据:原文对two issues to consider的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:When considering data distribution patterns for your use cases, there are two issues to consider. First, you should evaluate the acceptable delay between making operational changes and having them reflected in reads. For example, an application that needs end-of-day data has different requirements than an application that requires data to be delivered within a one-minute time window. Second, you should evaluate the need for periodic