anchor.diff:  }
   ----
   
  -which is the same as we have seen in the `JSON` with schema example.
  +Which is the same as we have seen in the "JSON with schema" example.
   
   The connector registration request differs in a few lines from the standard one:
   
   [source,json]
   ----
  -        (1) "key.converter": "io.apicurio.registry.utils.converter.ExtJsonConverter",
  -        (2) "key.converter.apicurio.registry.url": "http://apicurio:8080",
  -        (3) "key.converter.apicurio.registry.global-id": "io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy",
  -        (1) "value.converter": "io.apicurio.registry.utils.converter.ExtJsonConverter",
  -        (2) "value.converter.apicurio.registry.url": "http://apicurio:8080",
  -        (3) "value.converter.apicurio.registry.global-id": "io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy"
  -----
  -
  -. Apicurio JSON converter is used as both key and value converter
  -. Option points to the actual Apicurio registry endpoint
  -. This setting ensures that it is posible to automatically register the schema id which is typical setting in Debezium deployment
  +...
  +"key.converter": "io.apicurio.registry.utils.converter.ExtJsonConverter", <1>
  +"key.converter.apicurio.registry.url": "http://apicurio:8080", <2>
  +"key.converter.apicurio.registry.global-id":
  +    "io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy", <3>
  +
  +"value.converter": "io.apicurio.registry.utils.converter.ExtJsonConverter", <1>
  +"value.converter.apicurio.registry.url": "http://apicurio:8080", <2>
  +"value.converter.apicurio.registry.global-id":
  +    "io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy" <3>
  +...
  +----
  +<1> Apicurio JSON converter is used as both key and value converter
  +<2> Option points to the actual Apicurio registry endpoint
  +<3> This setting ensures that it is posible to automatically register the schema id which is typical setting in Debezium deployment
   
   === Avro Converter
   
  -So far we have demonstrated serialization of message into the `JSON` format only.
  -While `JSON` format has a lot of advantages like easy human readibility it still contains a lot of content unrelated to the data itself.
  -
  -To transfer really only the data without any significant overhead it is useful to use binary format serialization like Avro format.
  -In this case, we would pack the data only without any field names and other ceremony and again the message will contain a reference to a schema stored in the registry.
  +So far we have demonstrated serialization of messages into the JSON format only.
  +While using the JSON format with the registry has a lot of advantages, like easy human readability, it's still not very space-efficient.
  +
  +To transfer really only the data without any significant overhead, it is useful to use binary format serialization like Avro format.
  +In this case, we would pack the data only without any field names and other ceremony, and again the message will contain a reference to a schema stored in the registry.
   
   Let's look at how easily the Avro serialization can be used with Apicurio's Avro converter.
   
  
positive.code: 
  [source,bash]
  ----
  $ docker run --rm --tty   --network tutorial_default debezium/tooling bash -c 'http http://apicurio:8080/ids/64 | jq .'
  $ docker run --rm --tty   --network tutorial_default debezium/tooling bash -c 'http http://apicurio:8080/artifacts/dbserver1.inventory.customers-value | jq .'
  ----
  
  results in the same schema description:
  
negative.code: }
  ----
  
  The connector registration request also differs from the standard one in a handful of lines:
  
  [source,json]
  ----
  ...
  "key.converter": "io.apicurio.registry.utils.converter.AvroConverter", <1>
  "key.converter.apicurio.registry.url": "http://apicurio:8080", <2>
  "key.converter.apicurio.registry.converter.serializer":
      "io.apicurio.registry.utils.serde.AvroKafkaSerializer", <3>
  "key.converter.apicurio.registry.converter.deserializer":
      "io.apicurio.registry.utils.serde.AvroKafkaDeserializer", <3>
  "key.converter.apicurio.registry.global-id":
      "io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy", <4>
  "key.converter.apicurio.registry.id-handler":
      "io.apicurio.registry.utils.serde.strategy.ConfluentIdHandler", <5>
  
  "value.converter": "io.apicurio.registry.utils.converter.AvroConverter", <1>
  "value.converter.apicurio.registry.url": "http://apicurio:8080", <2>
  "value.converter.apicurio.registry.converter.serializer":
      "io.apicurio.registry.utils.serde.AvroKafkaSerializer", <3>
  "value.converter.apicurio.registry.converter.deserializer":
      "io.apicurio.registry.utils.serde.AvroKafkaDeserializer", <3>
  "value.converter.apicurio.registry.global-id":
      "io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy", <4>
  "value.converter.apicurio.registry.id-handler":
      "io.apicurio.registry.utils.serde.strategy.ConfluentIdHandler" <5>
  ...
  ----
  <1> Apicurio Avro converter is used as both key and value converter
  <2> Option points to the actual Apicurio registry endpoint
  <3> Prescribe which serializer and deserializer should be used by the converter
  <4> This setting ensures that it is posible to automatically register the schema id which is typical setting in Debezium deployment
  <5> This option is necessary only if we want to ensure binary compatibility with non-Apicurio aware tools like `kafkacat`
  
  == Conclusion
  
  In this article we discussed multiple approaches to message/schema association.
  The Apicurio registry was presented as a solution for schema sotrage and versioning and we have demonstrated how Apicurio can be integrated with Debezium connectors to efficiently deliver messages with schema to the consumer.
  You can find a complete example for using the Debezium connectors together with the Apicurio registry in the https://github.com/debezium/debezium-examples/tree/master/tutorial#using-mysql-and-apicurio-registry[tutorial] project of the Debezium examples repository on GitHub.
  
  == About Debezium
  
  