知识卡片

普通读书笔记卡 · 3406

CQRS用事件连接读写模型

理解等级:高级

命令侧可维护关系型真源,事件流再构建搜索或查询模型,让读写各用合适存储。收益是伸缩和隔离,代价是最终一致、双写同步及运维复杂度;单一数据库足够时不必拆分。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    原书出处

    参考来源

    - 位置:《Principles of Software Architecture Modernization》第8章《Embracing New Technology》(源文件:`_epub-src/OPS/ch08.xhtml`,归一化正文 [54748:58890)) - 结论依据:原文以 MySQL、Kafka 与搜索索引说明 CQRS 的能力和复杂度。 - 原始内容:The CQRS architecture model, where you have one implementation path and storage system for writes/commands, and another for reads/queries, can be powerful. ( Figure 8.17 ) CQRS allows us to isolate reads and writes and therefore has better scalability and isolation, and allows you to use specific technologies that each use case might require; but it brings greater complexity as a result.