> For the complete documentation index, see [llms.txt](https://docs.zongsoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zongsoft.com/framework/messaging/projects.md).

# 按项目阅读

按 Kafka、RabbitMQ、MQTT、ZeroMQ 与 .storages 源码项目查找消息实现。

从具体 Broker 或源码目录进入时，使用本页定位包、配置与实现边界。现有[消息队列](/framework/messaging.md)继续承担跨实现比较和公共调用示例，[投递概念](/framework/messaging/concepts.md)与[可靠性专题](/framework/messaging/reliability.md)解释共同背景。

| 源码项目      | 文档                                                  | 负责什么                     |
| --------- | --------------------------------------------------- | ------------------------ |
| kafka     | [Kafka](/framework/messaging/projects/kafka.md)     | Kafka 客户端、主题分区与消费位点      |
| rabbit    | [RabbitMQ](/framework/messaging/projects/rabbit.md) | 交换机路由、队列与消费确认            |
| mqtt      | [MQTT](/framework/messaging/projects/mqtt.md)       | 设备发布订阅、主题过滤器与 QoS        |
| zero      | [ZeroMQ](/framework/messaging/projects/zero.md)     | 客户端、内置 Broker 与两种投递路径    |
| .storages | [消息存储](/framework/messaging/projects/storages.md)   | 数据库持久记录与供 Broker 使用的存储工厂 |

## 从角色理解组合

前四个项目提供消息通讯实现，.storages 提供可选的持久存储。以 ZeroMQ 为例，客户端、Broker 和数据库存储可能部署在不同进程或节点中；连接配置和存储配置分别服务于它们的角色。

{% hint style="info" %}
💡 名称相近的 Group、Queue、Topic 和确认操作在不同协议中可能具有不同含义。迁移项目时，先阅读目标项目的映射及限制，再复用公共业务处理器。
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zongsoft.com/framework/messaging/projects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.