anchor.diff:  ====
   The outbox event router SMT is not compatible with the MongoDB connector.
   
  -ifdef::community[]
   As an alternative, MongoDB users can run the xref:transformations/mongodb-outbox-event-router.adoc[MongoDB outbox event router SMT].
  -endif::community[]
   ====
   
   ifdef::product[]
  
positive.code: The outbox event router SMT supports arbitrary payload formats. The `payload` column value in an outbox table is passed on transparently. An alternative to working with JSON is to use Avro.
  This can be beneficial for message format governance and for ensuring that outbox event schemas evolve in a backwards-compatible way.
  
  ifdef::product[]
  NOTE: The use of Avro to format the message payload is a Technology Preview feature.
  endif::product[]
  
  How a source application produces Avro formatted content for outbox message payloads is out of the scope of this documentation.
  One possibility is to leverage the `KafkaAvroSerializer` class to serialize `GenericRecord` instances.
  To ensure that the Kafka message value is the exact Avro binary data,
  
negative.code: For more information, see xref:options-for-applying-the-transformation-selectively[Options for applying the transformation selectively].
  
  A connector can capture changes in more than one outbox table only if each outbox table has the same structure.
  
  See link:https://debezium.io/blog/2019/02/19/reliable-microservices-data-exchange-with-the-outbox-pattern/[Reliable Microservices Data Exchange With the Outbox Pattern] to learn about why the outbox pattern is useful and how it works.
  
  ifdef::community[]
  