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

# Messaging concepts

Core messaging concepts: Messages, Channels, Endpoints, and Gateways

Ecotone is built on a small set of messaging primitives drawn from [Enterprise Integration Patterns](https://www.enterpriseintegrationpatterns.com/). Higher-level features like Command/Event/Query buses, Aggregates, Sagas, and Projections are all composed from these building blocks.

If you have used Symfony Messenger or Laravel Queues, the mapping is roughly: a **Message** is the envelope you dispatch, a **Channel** is the transport (queue, in-memory, broker), an **Endpoint/Handler** is the code that processes the message, and a **Gateway** is the typed interface you call to send it.

{% content-ref url="/pages/-LwhsETO-LK-lIFYfQaN" %}
[Message](/messaging/messaging-concepts/message.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LwhsdVFXtDs4bqRr4w1" %}
[Message Channel](/messaging/messaging-concepts/message-channel.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LwJfOPi0OKWs5SCKm7r" %}
[Message Endpoints/Handlers](/messaging/messaging-concepts/message-endpoint.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M3NHe4spQAgGRiqowAY" %}
[Consumer](/messaging/messaging-concepts/consumer.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LwhtSYhgD4TE4lcvMhv" %}
[Messaging Gateway](/messaging/messaging-concepts/messaging-gateway.md)
{% endcontent-ref %}

{% content-ref url="/pages/xd0i4EAq0nyDiiHg2bq6" %}
[Inbound/Outbound Channel Adapter](/messaging/messaging-concepts/inbound-outbound-channel-adapter.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ecotone.tech/messaging/messaging-concepts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.