Compatibility types that keep producers and consumers in sync as schemas change

Confluent Schema Registry docs on schema evolution and backward, forward, full, and transitive compatibility modes.

Schema evolution means changing schemas over time while keeping producers and consumers compatible. Schema Registry compares new versions to prior ones using configurable compatibility types, with BACKWARD as the default. Rules differ by format (Avro, Protobuf, JSON Schema) and by how fields were originally defined.

Based on: Schema Evolution & Compatibility Types | Backward, Forward, Full, Transitive | Confluent Documentation · Confluent

• Schemas & Shapes
• Data Contracts
• Data Engineering
• Semantic Interoperability