Skip to content

Kafka development sandbox

Quarkus dev

If any Kafka-related extension is present (e.g. quarkus-smallrye-reactive-messaging-kafka), Dev Services for Kafka automatically starts a Kafka broker in dev mode and when running tests.

Kafka local

When using docker compose in the eda-quickstart repository, the compose starts one zookeeper and one Kafka broker locally using last Strimzi packaging, one Apicurio for schema registry and Kafdrop for UI.

In the docker compose the Kafka defines two listeners, for internal communication using the DNS name kafka on port 29092 and one listener for external communication on port 9092.

A container in the same network needs to access kafka via its hostname.

To start kafkacat and kafkacat doc to access sample consumer - producer

docker run -it --network=host edenhill/kafkacat -b kafka:9092 -L