# Messaging patterns

Ylem is a data streaming platform on steroids. And that allows you to use the most popular, agile, and advanced messaging patterns to empower your pipelines with best practices.

You don't need to program anything. Our UI and backend software take care of everything under the hood.

Take a look at the following best practice implementation of messaging patterns with Ylem and re-use them for your pipelines:

<table data-view="cards"><thead><tr><th></th><th data-hidden></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Datatype Channel</strong></td><td></td><td></td><td><a href="/pages/KHNJe6u1fU7hPCrqTOkU">/pages/KHNJe6u1fU7hPCrqTOkU</a></td><td><a href="/files/rJuzMwK8zeiVIYIMrKNt">/files/rJuzMwK8zeiVIYIMrKNt</a></td></tr><tr><td><strong>Message Dispatcher</strong></td><td></td><td></td><td><a href="/pages/dpTba0knFKJVrUyzM5zB">/pages/dpTba0knFKJVrUyzM5zB</a></td><td><a href="/files/iaVmB9oxSPPb5fzdLrWj">/files/iaVmB9oxSPPb5fzdLrWj</a></td></tr><tr><td><strong>Messaging Bridge</strong></td><td></td><td></td><td><a href="/pages/yaqmBv8wS2X71HKtVgxf">/pages/yaqmBv8wS2X71HKtVgxf</a></td><td><a href="/files/jNpRw7OAoOQGVvsZiEbK">/files/jNpRw7OAoOQGVvsZiEbK</a></td></tr><tr><td><strong>Message Bus</strong></td><td></td><td></td><td><a href="/pages/ZTVHAWEa03i2DhIkQlSu">/pages/ZTVHAWEa03i2DhIkQlSu</a></td><td><a href="/files/d8My2zR3mjMfQNEutK7l">/files/d8My2zR3mjMfQNEutK7l</a></td></tr><tr><td><strong>Message Filter</strong></td><td></td><td></td><td><a href="/pages/qpRxqhkKgNBr4j1MsPWf">/pages/qpRxqhkKgNBr4j1MsPWf</a></td><td><a href="/files/M9TiCcGVG4Wrj5K6HUNF">/files/M9TiCcGVG4Wrj5K6HUNF</a></td></tr><tr><td><strong>Message Router</strong></td><td></td><td></td><td><a href="/pages/XGL1gQQ2S5YpTWqzMdNb">/pages/XGL1gQQ2S5YpTWqzMdNb</a></td><td><a href="/files/rJuzMwK8zeiVIYIMrKNt">/files/rJuzMwK8zeiVIYIMrKNt</a></td></tr><tr><td><strong>Point-to-Point Channel</strong></td><td></td><td></td><td><a href="/pages/rTyfrUzrZ0VGQE3lswsH">/pages/rTyfrUzrZ0VGQE3lswsH</a></td><td><a href="/files/zS3V5oH35Y7oyK1Ekcg4">/files/zS3V5oH35Y7oyK1Ekcg4</a></td></tr><tr><td><strong>Publish-Subscribe Channel</strong></td><td></td><td></td><td><a href="/pages/jLR3kQFCLHGydrZHyZxI">/pages/jLR3kQFCLHGydrZHyZxI</a></td><td><a href="/files/7OulViwdn3WYtInVh0Sr">/files/7OulViwdn3WYtInVh0Sr</a></td></tr><tr><td><strong>Pull-Push</strong></td><td></td><td></td><td><a href="/pages/JO7yCERk0IvyJuffLx23">/pages/JO7yCERk0IvyJuffLx23</a></td><td><a href="/files/EfLnKsxxepNXicAbuBQ6">/files/EfLnKsxxepNXicAbuBQ6</a></td></tr></tbody></table>

More information about the messaging patterns can be found in the [Enterprise Integration Patterns](https://www.enterpriseintegrationpatterns.com/patterns/messaging/) book.


---

# Agent Instructions: 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:

```
GET https://docs.ylem.co/use-cases/messaging-patterns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.