Dev Services for Kafka
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.
So, you don’t have to start a broker manually.
The application is configured automatically.
|Because starting a Kafka broker can be long, Dev Services for Kafka uses Redpanda, a Kafka compatible broker which starts in ~1 second.|
Dev Services for Kafka is automatically enabled unless:
quarkus.kafka.devservices.enabledis set to
all the Reactive Messaging Kafka channels have the
Dev Services for Kafka relies on Docker to start the broker.
If your environment does not support Docker, you will need to start the broker manually, or connect to an already running broker.
You can configure the broker address using
Most of the time you need to share the broker between applications. Dev Services for Kafka implements a service discovery mechanism for your multiple Quarkus applications running in dev mode to share a single broker.
Dev Services for Kafka starts the container with the
If you need multiple (shared) brokers, you can configure the
quarkus.kafka.devservices.service-name attribute and indicate the broker name.
It looks for a container with the same value, or starts a new one if none can be found.
The default service name is
Sharing is enabled by default in dev mode, but disabled in test mode.
You can disable the sharing with
By default, Dev Services for Kafka picks a random port and configures the application.
You can set the port by configuring the
Note that the Kafka advertised address is automatically configured with the chosen port.
Dev Services for Kafka uses:
You can select any version from https://hub.docker.com/r/vectorized/redpanda:
|Dev Services for Kafka only support Redpanda.|
You can configure the Dev Services for Kafka to create topics once the broker is started. Topics are created with given number of partitions and 1 replica.
The following example creates a topic named
test with 3 partitions, and a second topic named
messages with 2 partitions.
If a topic already exists with the given name, the creation is skipped, without trying to re-partition the existing topic to a different number of partitions.
You can configure timeout for Kafka admin client calls used in topic creation using
quarkus.kafka.devservices.topic-partitions-timeout, it defaults to 2 seconds.