Apache Kafka® Streams example applications for Avro

What is here

This repository contains four example Apache Kafka® Streams applications, which read and process Apache Avro™ messages. They demonstrate use of Generic and Specific Avro Serdes, logging, copying and filtering messages.

All default to reading from a topic called logistics_data_gen.

If you're using an Aiven for Apache Kafka service, then the Sample data generator for "Logistics" will write appropriate messages to the logistics_data_gen topic.

All message values use the Confluent Wire Format, which means the schema id is inserted before each value. This is sometimes also referred to as AvroConfluent. This means that the Serdes (serialize/deserialize) code can look the schema up in a schema registry, and all the apps take advantage of that.

1. GenericLogApp.java

   This uses a GenericAvroSerde to read each message value, and logs it. It does not write to an output topic.

2. GenericCopyApp.java

   This uses a GenericAvroSerde to read each message value, and copies that message to a different topic, using the same Serde. It defaults to writing to the topic logistics_data_copied.

The next two applications assume that the incoming messages match the schema in logistics_gen.avsc, corresponding to the messages generated by the Sample data generator for "Logistics".

3. GenericFilterApp.java

   This uses a GenericAvroSerde to read each message value.

   • It ignores messages where the state is not Delivered.
   • It writes messages with values timeUtc (instead of time_utc), trackingId (instead of tracking_id), carrier and manifest.

   It writes those altered messages to the output topic using a SpecificAvroSerde and the schema in logistics_delivered.avsc. The output topic defaults to logistics_data_delivered.

4. SpecificFilterApp.java

   This is identical to GenericFilterApp.java except that it uses a SpecificAvroSerde and the schema in logistics_gen.avsc. to read each message value.

For those applications that read from and write to a topic, both topics must be in the same Kafka application.

The applications are designed to be run in a container - a Dockerfile and associated run scripts (run.sh and setup_auth) are provided.

By default the container and scripts will run the GenericLogApp, which should work for any Avro messages. You can choose a different app using the APP_NAME environment variable, either at the docker build command line, or by editing the Dockerfile itself.

The project uses Gradle and Groovy for configuration and building.

Running the container

Download the URL and the certificates for the Kafka service.

Set an environment variable for the Kafka service URL - something like

export KAFKA_BOOTSTRAP_SERVERS=<service uri>

or in the Fish shell

set -x KAFKA_BOOTSTRAP_SERVERS <service uri>

Do the same for the schema registry host, port and password (the program defaults to the standard schema Karapace username of avnadmin, so we don't need to specify that).

export SCHEMA_REGISTRY_HOST=<schema registry host>

export SCHEMA_REGISTRY_PORT=<schema registry port>

export SCHEMA_REGISTRY_PASSWORD=<schema registry password>

(the Fish shell equivalents are left as an exercise for Fish shell users:).)

Set an environment variable to the content of each certificate file.

Typically,

1. Download the certificate files for the Kafka service (ca.pem, service. cert and service.key). For an Aiven for Kafka service you can do this from the Connection information in the service Overview.
2. Put the files into a directory called certs and use one of the convenience shell scripts to read the content of those files and set the environment variables:

   source prep_cert_env.sh

   or for Fish

   source prep_cert_env.fish

1. To build a container image for the default GenericLogApp:

   docker build -t appimage .

2. To build a container image for a specific app (for instance, GenericFilterApp):

   docker build --build-arg APP_NAME=GenericFilterApp -t appimage .

Run the container image:

docker run -d --name kafka-streams-container -p 3000:3000 \
        -e KAFKA_BOOTSTRAP_SERVERS=$KAFKA_BOOTSTRAP_SERVERS \
        -e KAFKA_CA_CERT="$KAFKA_CA_CERT" \
        -e KAFKA_ACCESS_CERT="$KAFKA_ACCESS_CERT" \
        -e KAFKA_ACCESS_KEY="$KAFKA_ACCESS_KEY" \
        -e SCHEMA_REGISTRY_HOST=$SCHEMA_REGISTRY_HOST \
        -e SCHEMA_REGISTRY_PORT=$SCHEMA_REGISTRY_PORT \
        -e SCHEMA_REGISTRY_USERNAME=$SCHEMA_REGISTRY_USERNAME \
        -e SCHEMA_REGISTRY_PASSWORD=$SCHEMA_REGISTRY_PASSWORD \
        -e EXACTLY_ONCE=false \
        appimage

We don't actually use the -p 3000:3000 port for anything at the moment.

Several of those environment variable arguments have defaults, so you can leave them off if you're happy with the default:

• SCHEMA_REGISTRY_USERNAME - run.sh defaults this to avnadmin
• INPUT_TOPIC - the program has a default
• OUTPUT_TOPIC - the program has a default
• EXACTLY_ONCE - run.sh defaults this to false.

Command line arguments for the Java app

All variants of the Java app take the following arguments (of course OUTPUT_TOPIC is not used by the Log app). Common code to handle these is in Config.java. The names chosen match the environment variables used by the container file and run.sh.

• -DKAFKA_BOOTSTRAP_SERVERS - the URL for the Kafka service.
• -DKAFKA_CA_CERT - the contents of the ca.pem file.
• -DKAFKA_ACCESS_CERT - the contents of the service.cert file.
• -DKAFKA_ACCESS_KEY - the contents of the service.key file.
• -DSCHEMA_REGISTRY_URL - the URL for the schema registry. run.sh sets this to https://${SCHEMA_REGISTRY_HOST}:${SCHEMA_REGISTRY_PORT}
• -DSCHEMA_REGISTRY_USERNAME - the user name for accessing the schema registry. This defaults to avnadmin, which is the default user name for Karapace.
• -DSCHEMA_REGISTRY_PASSWORD - the password for accessing the schema registry
• -DINPUT_TOPIC - the input topic name. This defaults to logistics_data_gen, which is the name of the topic written to by the Logistics data stream creator.
• -DOUTPUT_TOPIC - the output topic name. This defaults to logistics_data_delivered for the two filter programs, and logistics_data_copied for the copy program.
• -DEXACTLY_ONCE - request exactly once semantics. A value of true requests exactly once semantics, a value of false, an empty string or the absence of this property does not. The value is case insensitive. Any other value is an error.

The container file and how it works

This is a two stage container file.

The APP_NAME variable determines which app is being built and run. It defaults to GenericLogApp (which will work for any input topic).

The first stage builds a fat (uber) JAR for the program. This minimises the size of the executable to be passed to the second stage.

It uses jdeps and jlink to work out the dependencies that are not in the JAR file, and extract a minimum JRE from the larger JRE in provided by the operating system used in that first stage.

The second stage then downloads rocksdb (used by Kafka Streams).

It then copies over the minimal JRE prepared in the first stage, and the fat JAR itself, as well as the run.sh and setup_auth.sh files, and finally runs the run.sh script.

The run.sh and setup_auth.sh files

The run.sh file expects the following environment variables as input you'll recognise all but APP_NAME from the instructions on running the container and the Java app itself):

• KAFKA_BOOTSTRAP_SERVERS - the URL of the Kafka service we're using
• KAFKA_CA_CERT - the contents of the ca.pem file
• KAFKA_ACCESS_CERT - the contents of the service.cert file
• KAFKA_ACCESS_KEY - the contents of the service.key file
• SCHEMA_REGISTRY_HOST - the host for the schema registry. This must not include a leading https:// - it must just be the host name.
• SCHEMA_REGISTRY_PORT - the port for the schema registry
• SCHEMA_REGISTRY_USERNAME - the user name for accessing the schema registry. This is optional and if it is not given, a value of avnadmin will be assumed
• SCHEMA_REGISTRY_PASSWORD - the password for accessing the schema registry
• INPUT_TOPIC - the input topic name. This is optional as the Java app has a sensible default. logistics_data_gen.
• OUTPUT_TOPIC - the output topic name. This is optional as the Java app has a sensible default.
• EXACTLY_ONCE - whether exactly once semantics is wanted. This is optional and if it is not given, defaults to false. Request true if you want exactly once semantics.
• APP_NAME - the name of the application to run. This is optional and defaults to GenericLogApp.

It sources the setup_auth.sh script which makes sure that the KAFKA_CA_CERT, KAFKA_ACCESS_CERT and KAFKA_ACCESS_KEY environment variables contain data that is correctly split into lines.

Finally the run.sh script runs the fat Java JAR with the necessary arguments.

Building the program

We use a fat (uber) JAR in the container, so that all of the programs non-standard dependencies (the ones not provided by the JRE) are frozen into the final executable.

You can build that fat JAR file with

gradle ${APP_NAME}UberJar

where $APP_NAME is one of GenericLogApp, GenericCopyApp, GenericFilterApp or SpecificFilterApp -- for instance:

gradle SpecificFilterAppUberJar

(See app/build.gradle for the definition of the UberJar tasks.)

If you want to run the app using the provided run.sh script, then you'll also need to copy the result to the top-level directory

cp app/build/libs/$APP_NAME-uber.jar .

Exactly once semantics

With a normal Kafka Streams application, it is possible that a message might be processed once, more than once, or never at all (networks are unreliable, services can crash, and so on).

Exactly once semantics (EOS) in Kafka Streams guarantees that each message will be processed once, no more and no less. It's been available since 2017.

There is quite a lot of good documentation about exactly once semantics for Kafka Streams - the following is by no means an exhaustive list.

See Confluent's Exactly-Once Semantics Are Possible: Here’s How Kafka Does It (2017/2025) for a good introduction to how this works.

The Kafka Streams Core Concepts document (this link is for Apache Kafka 4.1.x which is current at time of writing) is also pretty good. It talks about exactly once in the Processing Guarantees section.

Zeinab Dashti's Developer Guide to Achieve Transactional Processing in Kafka Streams (2025) is good at the pragmatics, and notes that:

When processing.guarantee=exactly_once_v2 is set, Kafka Streams automatically enforces the required producer and consumer configurations:

enable.idempotence=true (on the Kafka producer)
isolation.level=read_committed (on the Kafka consumer)

You don’t need to set these manually — doing so isn’t harmful if you match the required values, but Kafka Streams will log a warning or ignore conflicting settings.

and

Any external consumer reading from Kafka output topics that are written transactionally must configure:

isolation.level=read_committed

Kafka Streams enforces this by default within its topology, but it must be set explicitly for standalone consumers (e.g., Kafka Connect, other microservices). Without it, consumers could read uncommitted or aborted records, which may result in data duplication or inconsistency.

Running the unit tests

There are minimal unit tests for the four applications.

Run them with, for instance:

gradle clean cleanTest test

Running run.sh locally

It's possible to run the run.sh script locally, and indeed this is useful for testing. It's important to remember to

1. Copy the built app into the same directory as the run.sh script
2. Set the required various environment variables first - these are also documented at the top of the run.sh file.

For instance

./run.sh

or

APP_NAME=GenericFilterApp ./run.sh

or

APP_NAME=GenericCopyApp OUTPUT_TOPIC=logistics_copy ./run.sh

Visualising the messages

In the reporting directory there is a command line program report_messages.py which reads messages from both the input and output topics and shows them using a text UI.

It deliberately uses the same environment variables that are needed to run the actual application, with the exception of $SCHEMA_REGISTRY_URL, which it expects to embed the username and password. You can build that from the other environment variables:

https://${SCHEMA_REGISTRY_USERNAME}:${SCHEMA_REGISTRY_PASSWORD}@${SCHEMA_REGISTRY_HOST}:${SCHEMA_REGISTRY_PORT}

If you're using an Aiven for Kafka service, you can get the value from the Kafka service overview in the Aiven web console (as the Schema Registry Service URI), or using the command line

export SCHEMA_REGISTRY_URL=$(avn service get $KAFKA_SERVICE_NAME --json | jq -r '.connection_info.schema_registry_uri')

or for Fish shell

set -x SCHEMA_REGISTRY_URL (avn service get $KAFKA_SERVICE_NAME --json | jq -r '.connection_info.schema_registry_uri')

If all the environment variables are set up, then you can run it with

reporting/report_messages.py

Get help on what it does with

reporting/report_messages.py -h

In that same directory there is an experimental wrapper (serve.py) which allows it to be run as a web app in a Docker container.

For instance:

cd reporting

docker build -t report_image .

docker run -d --name report-messages-container -p 3000:3000 \
        -e KAFKA_BOOTSTRAP_SERVERS=$KAFKA_BOOTSTRAP_SERVERS \
        -e KAFKA_CA_CERT=$KAFKA_CA_CERT \
        -e KAFKA_ACCESS_CERT=$KAFKA_ACCESS_CERT \
        -e KAFKA_ACCESS_KEY=$KAFKA_ACCESS_KEY \
        -e SCHEMA_REGISTRY_URL=$SCHEMA_REGISTRY_URL \
        report_image

End to end example using Aiven for Kafka

Note For trying out this Kafka Streams app, a free Aiven for Kafka service will work just fine. The instructions below show how to use that, as well as how to use a paid service if that's more suitable.

It's possible to do everything in this section using the Aiven web console, but for documentation purposes here I shall use the avn command line tool.

Since avn is a Python tool, make sure you're in a virtual environment and download it:

python -m venv venv
source venv/bin/activate    # If you're using fish, activate.fish
pip install aiven-client

Retrieve an Aiven session token (see the documentation) and login, using the email address you logged in to the console with, and pasting the token when prompted:

avn user login <your-email> --token

For convenience, set the project to your current project - this means you don't have to specify it on every command:

avn project switch <project-name>

Set an environment variable for the service name - perhaps something like "kafka-streams-example"

export KAFKA_SERVICE_NAME=<service name>

or for Fish shell

set -x KAFKA_SERVICE_NAME <service name>

Create the Aiven for Kafka service. We'll show how to create a free or paid service. There are notes about each command after the command.

1. For trying out this app, a free or developer tier Aiven for Kafka service will work just fine.

   Create the a free tier service using the following command:

   avn service create $KAFKA_SERVICE_NAME          \
           --service-type kafka                    \
           --cloud do-ams                          \
           --plan free-0                           \
           -c schema_registry=true                 \
           -c kafka.auto_create_topics_enable=true

   Notes

   • The details of how the free and developer tier cloud and plan are specified at the command line may change. This is one case where it's actually simpler to use the Aiven web console, as there you just choose the Kafka tier and then what part of the world you want.

     Alternatively, use the Aiven MCP and ask for what you want.

   • -c schema_registry=true says we want to enable the Karapace schema registry. This is also free, and we need it to handle Avro messages.

   • -c kafka.auto_create_topics_enable=true says we want producers to be able to create topics. You don't want this in production, but it's often a good idea in development, and it means the output topics will get created as we need them.

2. If you prefer (maybe you're already using your free Aiven for Kafka service for something else and don't want to add new topics to it), you can instead create a Professional tier (paid) service. For that, use a command like the following:

   avn service create $KAFKA_SERVICE_NAME          \
           --service-type kafka                    \
           --cloud aws-eu-west-1                   \
           --plan startup-4                        \
           --no-project-vpc                        \
           -c schema_registry=true                 \
           -c kafka.auto_create_topics_enable=true

   Notes

   • Choose a cloud and plan that match your needs. There's no need to go for anything above the minimum plan (startup-4 in this case).
   • In the case of this cloud and region, I knew there was a VPC (virtual private cloud) available to my organization, so I needed to tell the command I did not want to use it. It doesn't hurt to specify th
   • The last two switches are the same as in the free example above.

While that's running, get the service URL for the new service

export KAFKA_BOOTSTRAP_SERVERS=$(avn service get $KAFKA_SERVICE_NAME --format '{service_uri}')

or for Fish shell

set -x KAFKA_BOOTSTRAP_SERVERS (avn service get $KAFKA_SERVICE_NAME --format '{service_uri}')

Get the schema registry (Karapace) host

export SCHEMA_REGISTRY_HOST=$(avn service get $KAFKA_SERVICE_NAME --json | jq -r '.components[] | select(.component == "schema_registry") .host')

or for Fish shell

set -x SCHEMA_REGISTRY_HOST (avn service get $KAFKA_SERVICE_NAME --json | jq -r '.components[] | select(.component == "schema_registry") .host')

Get the schema registry (Karapace) port

export SCHEMA_REGISTRY_PORT=$(avn service get $KAFKA_SERVICE_NAME --json | jq -r '.components[] | select(.component == "schema_registry") .port')

or for Fish shell

set -x SCHEMA_REGISTRY_PORT (avn service get $KAFKA_SERVICE_NAME --json | jq -r '.components[] | select(.component == "schema_registry") .port')

Get the schema registry password

export SCHEMA_REGISTRY_PASSWORD=$(avn service get $KAFKA_SERVICE_NAME --json | jq -r '.users[0].password')

or for Fish shell

set -x SCHEMA_REGISTRY_PASSWORD (avn service get $KAFKA_SERVICE_NAME --json | jq -r '.users[0].password')

We assume the default username for the schema registry, so don't need to look that up, but if you do need it then you can get it with

export SCHEMA_REGISTRY_USERNAME=$(avn service get $KAFKA_SERVICE_NAME --json | jq -r '.users[0].username')

or for Fish shell

set -x SCHEMA_REGISTRY_USERNAME (avn service get $KAFKA_SERVICE_NAME --json | jq -r '.users[0].username')

Wait for it to reach Running state

avn service wait $KAFKA_SERVICE_NAME

Once the Kafka service is running, you can create the two topics if you're not using the standard names, but

1. The Logistics sample data stream generator will create logistics_data_gen topic for you.
2. The -c kafka.auto_create_topics_enable=true specified when creating the service means the logistics_data_delivered topic will get created when the program tries to write to it.

avn service topic-create    \
    --partitions 1          \
    --replication 2         \
    $KAFKA_SERVICE_NAME logistics_data_gen

avn service topic-create    \
    --partitions 1          \
    --replication 2         \
    $KAFKA_SERVICE_NAME logistics_data_delivered

Download the certification files (it will create the directory if necessary)

avn service user-creds-download $KAFKA_SERVICE_NAME --username avnadmin -d certs

ls certs

should report

ca.pem  service.cert  service.key

Set the environment variables for the certificate file contents

source prep_cert_env.sh

or for Fish shell

source prep_cert_env.fish

And now you're ready to run the program, either via ./run.sh or via Docker.

Deploying with compose.specific.yaml

If all of the environment variables described above have been set, then the compose file compose.specific.yaml can be used to deploy the Kafka Streams service. This works well when using an Aiven for Apache Kafka service, as described in the previous section.

docker compose -f compose.specific.yaml up

Also, if you specify the APP_NAME environent variable, you can override the application name set using ARG at the top of the Dockerfile:

APP_NAME=GenericFilterApp docker compose -f compose.specific.yaml up

Deploying as an Aiven App

Note: At the moment (July 2026) Aiven Apps is in Limited Availability (LA). See Aiven Apps for more information and to request access.

Create a fork that does what you want

Fork the repository and create a branch to work on.

Edit the Dockerfile to set which Kafka Streams app you want to run, GenericLogApp, GenericCopyApp, GenericFilterApp or SpecificFilterApp, by changing the line

ARG APP_NAME=GenericLogApp

Make a note of the value specified for APP_NAME - you will need it when you are setting up the configuration for the App service when deploying to Aiven Apps, below.

If you want to alter what the Java code does, this is the time to do that as well.

If you're working on a local clone of the repository, remember to push to the upstream, so that Aiven Apps will be able to see your changes.

Create an Aiven for Kafka service

This can be done using the Aiven console, or with the command line, as explained in the previous section.

Create the input and output topics, again as described in the previous section.

Deploy to Aiven Apps

The following is a summary - check the documentation for the most up-to-date information.

1. In the Aiven Console go to your project and click Applications.

2. Click Deploy app.

3. If you haven’t already done so, use Connect another account to connect your GitHub account to your Aiven organization.

4. Select your Account, your forked repository, and the appropriate branch.

5. Click Next.

6. Select the manifest file compose.aiven.yaml and click Scan.

7. On the card for the Kafka service, click the paired arrows icon , and choose the Kafka service you created earlier.

8. On the card for the Kafka Streams service, click the pen icon to edit its configuration.

   • Check that the application Name is recognisable, and edit it if necessary. The aim is to have a name that you’ll recognise and be able to find later.
   • In the Environment variables section:
     • Set the value for APP_NAME to the same value you set in the Dockerfile above (the appropriate one of GenericLogApp, GenericCopyApp, GenericFilterApp or SpecificFilterApp).
     • Set the INPUT_TOPIC name to logistics_data_gen
     • Set the OUTPUT_TOPIC name to "" (for GenericLogApp), logistics_data_copied (for GenericCopyApp) or logistics_data_delivered (for either FilterApp).
     • Copy the SCHEMA_ values from the Schema registry tab on the Kafka Service Overview page (in the Aiven web console). For the password, use the toggle switch to make it a secret.
     • Do not change the values for FAT_JAR_NAME or JAVA_HOME.

9. To deploy the app services, click Deploy.

The Kafka Streams app will start to build. See its progress in the Build logs tab. It will connect to the Kafka service when it runs, and you can then see its progress in the Runtime logs tab.

Note setting the value of APP_NAME for the Kafka Streams service is necessary with the current (2026-07) version of Aiven Apps, which does not process or allow setting container file ARGS values.

This is only really a problem because the Dockerfile has been designed to support multiple applications - if it was for just (for instance) GenericFilterApp, the issue would not arise.

If the application Runtime logs report a failure because it can’t find the “uber” JAR file, for instance

Error: Unable to access jarfile ./GenericCopyApp-uber.jar

then that probably means you didn’t set APP_NAME to the same value as it has in the Dockerfile.