anchor.diff:  
   A system that wants to use Avro serialization needs to complete two steps:
   
  -* Deploy a https://github.com/Apicurio/apicurio-registry[Apicurio API/Schema Registry] instance
  +* Deploy an https://github.com/Apicurio/apicurio-registry[Apicurio API/Schema Registry] instance
   * Install the Avro converter from https://repo1.maven.org/maven2/io/apicurio/apicurio-registry-distro-connect-converter/{apicurio-version}/apicurio-registry-distro-connect-converter-{apicurio-version}-converter.tar.gz[the installation package] into Kafka's _libs_ directory or directly into a plug-in directory
   * Use thes the following properties to configure Apache Connect instance
   
  
positive.code: Over time, the change events captured by Debezium connectors and written by Kafka Connect into a topic may have different versions of the same schema,
  and Avro serialization makes it far easier for consumers to adapt to the changing schema.
  
  The open-source project https://github.com/Apicurio/apicurio-registry[Apicurio Registry] provides several components that work with Avro:
  
  * An Avro converter that can be used in Kafka Connect workers to map the Kafka Connect schemas into Avro schemas and to then use those Avro schemas to serialize the message keys and values into the very compact Avro binary form.
  
negative.code: Note that Kafka Connect internally always uses the JSON key/value converters for storing configuration and offsets.
  
  == Debezium Container Images
  
  Deploy an Apicurio Registry instance (this example uses a non-production in-memory instance):
  
  