anchor.diff:  $ docker-compose -f docker-compose-mysql-apicurio.yaml up -d --build
   
   # Start the connector
  -curl -i -X POST -H "Accept:application/json" -H  "Content-Type:application/json" http://localhost:8083/connectors/ -d @register-mysql-apicurio-converter-json.json
  +curl -i -X POST -H "Accept:application/json" \
  +    -H  "Content-Type:application/json" \
  +    http://localhost:8083/connectors/ -d @register-mysql-apicurio-converter-json.json
   
   # Read content of the first message
  -$ docker run --rm --tty   --network tutorial_default debezium/tooling bash -c 'kafkacat -b kafka:9092 -C -o beginning -q -t dbserver1.inventory.customers -c 1 | jq .'
  +$ docker run --rm --tty \
  +    --network tutorial_default debezium/tooling bash \
  +    -c 'kafkacat -b kafka:9092 -C -o beginning -q -t dbserver1.inventory.customers -c 1 | jq .'
   ----
   
   The resulting message should look like:
  
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: }
  ----
  
  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]
  ----
  ...
  "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 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.
  
  