知识卡片

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

事件命令查询应分责

理解等级:高级

事件表达已发生事实,命令请求执行可能被拒绝的动作,查询不修改业务状态。把命令职责随意跨多个应用拆散会使事务完整性难以保证,需要显式失败与补偿安排。流式复杂度应由可量化业务价值证明,而非把实时当作默认要求。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

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

      Segregate events, notifications, queries, and commands. You might want to formulate principles for each of these: for example, queries must leave the state of the system unchanged, or commands must create, update, or delete some data. Commands must explicitly stay within the transactional boundaries. One of the biggest risks of distributing the concerns of processing commands across multiple applications is that consistency or transactional integrity

    参考来源

    - 位置:《Data Management at Scale》第06章《Event and Notification Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch06.html) - 结论依据:原文对Segregate events, notifications, queries的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。 - 原始内容:Segregate events, notifications, queries, and commands. You might want to formulate principles for each of these: for example, queries must leave the state of the system unchanged, or commands must create, update, or delete some data. Commands must explicitly stay within the transactional boundaries. One of the biggest risks of distributing the concerns of processing commands across multiple applications is that consistency or transactional integrity