> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/legacy-documentation/ew-dos-technology-components-2023/decentralized-data-hub-ddhub/ddhub-message-broker.md).

# DDHub Message Broker

## Overview

DDHub Message Broker is a component that primarily provides message routing, persisting, and delivery for a seamless data exchange between participants within an energy market or supply chain.

The message broker promotes sovereignty of participants by:

* The broker does not have authority or logic which assumes the power of the participants
* No one except the participant themselves can govern data exchange channels and verify messages
* Encryption/decryption, signature validation, authorization, etc must be done under the participants domain ([Client Gateway](/legacy-documentation/ew-dos-technology-components-2023/decentralized-data-hub-ddhub/ddhub-client-gateway.md))

## DDHub Message Broker Component Diagram

<figure><img src="/files/I89iI5ImgWl4WvjuJDpK" alt=""><figcaption></figcaption></figure>

Below are the Message Broker components which need to be hosted to deploy a Decentralized Data Hub:

* Message Broker App
* NATS Jetstream and Jetstream Store to store small data messages (small messages up to 2 MB) and channel configurations
* Azure Blob (or other large file) Store for large data messages and delimited files converted into blobs, as well as file metadata
* RDBMS for message topic and schema management

<figure><img src="https://github.com/energywebfoundation/ewf-gitbook/blob/develop/.gitbook/assets/Screenshot%202023-05-02%20at%204.29.24%20PM.png" alt=""><figcaption></figcaption></figure>


---

# 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.energyweb.org/legacy-documentation/ew-dos-technology-components-2023/decentralized-data-hub-ddhub/ddhub-message-broker.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.