The English version of is the official project site. Translated sites are community supported on a best-effort basis.
Edit this Page

Servicios de desarrollo para Apicurio Registry

If an extension for schema registry, such as quarkus-apicurio-registry-avro or quarkus-confluent-registry-avro, is present, Dev Services for Apicurio Registry automatically starts an Apicurio Registry instance in dev mode and when running tests. Also, all Kafka channels in SmallRye Reactive Messaging are automatically configured to use this registry. This automatic configuration only applies to serializers and deserializers from Apicurio Registry serde libraries and Confluent Schema Registry serde libraries, because there properties are set:

# for Apicurio Registry serde
# for Confluent Schema Registry serde

Activación/desactivación de los servicios de desarrollo para el registro de Apicurio

Los Servicios de Desarrollo para el Registro de Apicurio se activan automáticamente a menos que:

  • quarkus.apicurio-registry.devservices.enabled se ajusta a false

  • mp.messaging.connector.smallrye-kafka.apicurio.registry.url está configurado

  • mp.messaging.connector.smallrye-kafka.apicurio.registry.url está configurado

  • todos los canales de Kafka de Mensajería Reactiva tienen el atributo apicurio.registry.url establecido

Dev Services for Apicurio Registry relies on Docker to start the registry. If your environment does not support Docker, you will need to start the registry manually, or use an already running registry. In such case, you can configure the registry URL for all Kafka channels in SmallRye Reactive Messaging with a single property. For Apicurio Registry serde, that is:

mp.messaging.connector.smallrye-kafka.apicurio.registry.url=... your Apicurio Registry URL...

Para Confluent Schema Registry serde, esto es:

mp.messaging.connector.smallrye-kafka.schema.registry.url=... your Confluent Schema Registry URL...

Registro compartido

Most of the time you need to share the registry between applications. Dev Services for Apicurio Registry implements a service discovery mechanism for your multiple Quarkus applications running in dev mode to share a single registry.

Dev Services for Apicurio Registry inicia el contenedor con la etiqueta quarkus-dev-service-apicurio-registry que se utiliza para identificar el contenedor.

If you need multiple (shared) registries, you can configure the quarkus.apicurio-registry.devservices.service-name attribute and indicate the registry 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 apicurio-registry.

Sharing is enabled by default in dev mode, but disabled in test mode. You can disable the sharing with quarkus.apicurio-registry.devservices.shared=false.

Ajuste del puerto

By default, Dev Services for Apicurio Registry picks a random port and configures the application. You can set the port by configuring the quarkus.apicurio-registry.devservices.port property.

Tenga en cuenta que los canales Kafka en la mensajería reactiva de SmallRye se configuran automáticamente con el puerto elegido.

Configuración de la imagen

Dev Services for Apicurio Registry uses apicurio/apicurio-registry-mem images. You can select any 2.x version from


Related content