> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/devops/microservices/service-runners/deploying-runners/samza-runners.md).

# Samza Runners

These runners are based on Samza library, receiving requests from Samza consumers (e.g. Kafka) and returning results on Samza producers (e.g. Kinesis).

All Samza configurations are applicable, and can be passed on to these runners using global runner elements.

## Sync Samza Event Runner

SyncSamzaEventRunner(*com.rierino.runner.samza.SyncSamzaEventRunner*) guarantees message order, with blocking properties for each message received.

Name of the input topic is used as the stream and the messages are used as the full event contents.

## Async Samza Event Runner

AsyncSamzaEventRunner(*com.rierino.runner.samza.AsyncSamzaEventRunner*) does not guarantee message order, as it provides certain level of parallelization.

Name of the input topic is used as the stream and the messages are used as the full event contents.

{% embed url="<https://samza.apache.org>" %}
Samza Page
{% endembed %}

{% hint style="info" %}
Samza runners can also communicate with Restful event runners (e.g. as a step inside a Saga flow), which results in synchronous event exchange with the remote runner.
{% endhint %}


---

# 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.rierino.com/devops/microservices/service-runners/deploying-runners/samza-runners.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.