# Use cases, patterns, templates, examples

- [Use cases](https://docs.ylem.co/use-cases/use-cases.-homepage.md)
- [Messaging patterns](https://docs.ylem.co/use-cases/messaging-patterns.md)
- [Datatype Channel](https://docs.ylem.co/use-cases/messaging-patterns/datatype-channel.md)
- [Message Dispatcher](https://docs.ylem.co/use-cases/messaging-patterns/message-dispatcher.md)
- [Messaging Bridge](https://docs.ylem.co/use-cases/messaging-patterns/messaging-bridge.md)
- [Message Bus](https://docs.ylem.co/use-cases/messaging-patterns/message-bus.md)
- [Message Filter](https://docs.ylem.co/use-cases/messaging-patterns/message-filter.md)
- [Message Router](https://docs.ylem.co/use-cases/messaging-patterns/message-router.md)
- [Point-to-Point Channel](https://docs.ylem.co/use-cases/messaging-patterns/point-to-point-channel.md)
- [Publish-Subscribe Channel](https://docs.ylem.co/use-cases/messaging-patterns/publish-subscribe-channel.md)
- [Pull-Push](https://docs.ylem.co/use-cases/messaging-patterns/pull-push.md)
- [Functional use cases](https://docs.ylem.co/use-cases/functional-use-cases.md)
- [Streaming from Apache Kafka and messaging queues](https://docs.ylem.co/use-cases/functional-use-cases/streaming-from-apache-kafka-and-messaging-queues.md): Since Ylem is a real-time streaming platform, our goal is to provide you with a tool with which you can deliver your data from one place to another as fast as possible.
- [Streaming from APIs](https://docs.ylem.co/use-cases/functional-use-cases/streaming-from-apis.md)
- [Streaming from databases](https://docs.ylem.co/use-cases/functional-use-cases/streaming-from-databases.md)
- [Data orchestration, transformation and processing](https://docs.ylem.co/use-cases/functional-use-cases/data-orchestration-transformation-and-processing.md)
- [Usage of Python and Pandas](https://docs.ylem.co/use-cases/functional-use-cases/usage-of-python-and-pandas.md)
- [KPI Monitoring](https://docs.ylem.co/use-cases/functional-use-cases/kpi-monitoring.md)
- [OKRs and custom metrics](https://docs.ylem.co/use-cases/functional-use-cases/okrs-and-custom-metrics.md)
- [Data Issues & Incidents](https://docs.ylem.co/use-cases/functional-use-cases/data-issue-monitoring.md)
- [Reporting](https://docs.ylem.co/use-cases/functional-use-cases/reporting.md)
- [Other functional use cases](https://docs.ylem.co/use-cases/functional-use-cases/other-functional-use-cases.md)
- [Industry-specific use cases](https://docs.ylem.co/use-cases/industry-specific-use-cases.md)
- [Finance and Payments](https://docs.ylem.co/use-cases/industry-specific-use-cases/finance-and-payments.md)
- [E-commerce & Logistics](https://docs.ylem.co/use-cases/industry-specific-use-cases/e-commerce.md)
- [Customer Success](https://docs.ylem.co/use-cases/industry-specific-use-cases/customer-success.md)
- [Security, Risk, and Anti-Fraud](https://docs.ylem.co/use-cases/industry-specific-use-cases/security-risk-aml-and-fraud.md)
- [Anti-Money Laundering (AML)](https://docs.ylem.co/use-cases/industry-specific-use-cases/anti-money-laundering-aml.md)


---

# 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.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.