> For the complete documentation index, see [llms.txt](https://www.eaiguide.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.eaiguide.org/the-basics/types-of-application-integration/hub-and-spoke-integration-esb.md).

# Hub-and-Spoke Integration (ESB)

A hub-and-spoke model connects multiple systems (spokes) to a central hub. Central hub is also known as Enterprise Service Bus (ESB). Messages are exchanged between multiple systems via the central hub, which acts as a mediator of all messages from one central place. Rather than messages flowing [point to point](/the-basics/types-of-application-integration/point-to-point-integration.md) from one system to another, they all go through one central hub.

## **Hub**

Hub orchestrates all messages between systems. Its important function is to decouple the direct connection between multiple systems. This way, the systems do not have to know about the data formats and protocols of other systems.

Hub handles tasks such as message routing, transformation, enforcing business rules, security, data encryption and decryption, and other related Integration activities.

## **Spoke**

The spokes, as individual systems in the hub-and-spoke model, are responsible for sending and receiving information from other systems. They interact with the hub to send and receive messages and do not connect to another spoke directly.

If spokes connect with each other directly, it is called [point-to-point integration](/the-basics/types-of-application-integration/point-to-point-integration.md).

<figure><img src="/files/PaR2tmclRpdIU6cRN7mF" alt="" width="563"><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://www.eaiguide.org/the-basics/types-of-application-integration/hub-and-spoke-integration-esb.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.