# Samza Runners

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