Protocols
Saved & recent

Schema registry

Also called: message schema registry, Confluent Schema Registry

A schema registry stores and serves definitions of message structures, often with versions and compatibility checks. It helps producers and consumers agree on how to encode and interpret data. It is a service and coordination pattern, not one universal wire protocol. A registry manages schemas; the messaging system carries the business records.

For example, a Confluent Schema Registry subject tracks versions of a shipment event’s Avro schema. A producer proposes a new version, and the registry checks it against the configured compatibility policy before accepting it. Consumers use the appropriate schema to decode records. Passing a structural compatibility check does not prove that changed fields retain the same business meaning.

Related
Schema evolution, Apache Avro, Protocol Buffers
Further reading
Confluent — Schema Registry concepts
schema registry v1 → proposed v2 policy: backward producer broker consumer proposes schema v2 fetches schema shipment record shipment record schema metadata business event records stored in registry sent through broker
This example checks a proposed schema under a backward-compatibility policy. The registry serves schema metadata; the broker carries shipment records. Structural compatibility does not prove that business meaning is unchanged.

View in the full Protocols collection