> 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/multi-tenancy-support/advanced-queuing-strategies.md).

# Advanced Queuing Strategies

Advanced queuing strategies for multi-tenant message processing

A free-tier tenant fires 10,000 messages and your queue backlog blocks every other tenant for an hour. Or you onboard a premium tenant and want their messages on a dedicated channel without rewriting handlers. Or you're rolling out a deploy and want to drain one tenant's queue cleanly while others keep flowing.

These scenarios outgrow the static channel model. Ecotone's **Dynamic Message Channels** let you route, throttle, and isolate per tenant at runtime — picking the channel from a header, applying credit-based rate limits, or sending specific tenants to dedicated workers — without changing the handler code.

The full feature is documented under Asynchronous Handling, since the same primitives apply to non-tenant routing as well:

{% content-ref url="/pages/W1Ddrljy41zrP0GKodAt" %}
[Dynamic Message Channels](/modelling/asynchronous-handling/dynamic-message-channels.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/multi-tenancy-support/advanced-queuing-strategies.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.