anchor.diff:  Alternatively, you can serialize the message keys and values by using link:https://avro.apache.org/[Apache Avro].
   The Avro binary format is compact and efficient, and Avro schemas make it possible to ensure that the messages have the correct structure. Avro's schema evolution mechanism makes it possible to evolve the schemas over time, which is essential for {prodname} connectors that dynamically generate the message schemas to match the structure of the database tables. Over time, the change events captured by {prodname} connectors and written by Kafka Connect into a topic may have different versions of the same schema. Avro serialization makes it easier for consumers to adapt to the changing schema.
   
  +To use Apache Avro as the message format, you must deploy a schema registry that manages Avro message schemas and their versions. 
  +
   ifdef::product[]
   [IMPORTANT]
   ====
  
positive.code: // ModuleID: deploying-connectors-that-use-avro-in-debezium-containers
  == Deploying with {prodname} containers
  
  In your environment, you might want to use a {prodname} pre-built container to deploy a {prodname} connector that uses Avro serializaion. Follow the procedure here to do that. In this procedure, you build a {prodname} image in which {prodname} uses the Avro converter.  
  
  .Prerequisites
  
  
negative.code: +
  `oc create -f https://raw.githubusercontent.com/apicurio/apicurio-registry-operator/master/docs/resources/example-cr/in-memory.yaml`
  +
  The in-memory deployment is not suitable for production. Use the Apache Kafka persistence option for production. For more information, see {LinkServiceRegistryGetStart}[NameServiceRegistryGetStart].
  endif::product[]
  
  . Build a {prodname} container image that implements the Avro converter:
  