虽然我以前遇到过Kafka，但我最近才意识到Kafka可能被用作CQRS，事件存储的(基础)。

Kafka支持的一个主要观点是:

事件捕获/存储，当然是所有HA。 发布/订阅体系结构 能够重放事件日志，允许新的订阅者在事件发生后向系统注册。

不可否认，我不是100%精通CQRS /事件来源，但这似乎非常接近事件撕裂应该是什么。有趣的是:我真的找不到那么多关于Kafka被用作事件存储的信息，所以我可能遗漏了一些东西。

那么，Kafka还缺少什么东西来成为一个好的事件存储吗?这会有用吗?使用它的产品?对洞察力、链接等感兴趣?

基本上，系统的状态是根据系统曾经接收到的事务/事件来保存的，而不是像通常那样只保存系统的当前状态/快照。(可以把它想象成会计中的总账:所有交易最终加起来都是最终状态)这允许各种很酷的事情，但请仔细阅读所提供的链接。

我开始学习卡夫卡，在阅读过程中，我想到了一些问题:

When a producer is producing a message - it will specify the topic it wants to send the message to, is that right? Does it care about partitions? When a subscriber is running - does it specify its group id so that it can be part of a cluster of consumers of the same topic or several topics that this group of consumers is interested in? Does each consumer group have a corresponding partition on the broker or does each consumer have one? Are the partitions created by the broker, and therefore not a concern for the consumers? Since this is a queue with an offset for each partition, is it the responsibility of the consumer to specify which messages it wants to read? Does it need to save its state? What happens when a message is deleted from the queue? - For example, the retention was for 3 hours, then the time passes, how is the offset being handled on both sides?

我曾被要求评估RabbitMQ而不是Kafka，但发现很难找到一个消息队列比Kafka更适合的情况。有人知道在哪些用例中消息队列在吞吐量、持久性、延迟或易用性方面更适合吗?