# Schema Registry

> A shared list of event shapes. It stops a writer from breaking readers.

**Field:** Data Engineering  
**Category:** Ingestion & Streaming  
**Also known as:** Confluent Schema Registry, Event Schema Registry

## Think of it like

It is like a shared rule book for a game. Each player checks it. So no one plays by old rules.

## Definition

A schema registry is a shared store of the schemas used by events in a stream. A producer checks its schema against the registry before it sends. Each event carries a small schema ID instead of the full schema. Consumers look up that ID to read the event. The registry can refuse a new version that would break the readers.

## Example

A team adds a field to the order event. The registry checks it and accepts it, because old readers can skip the new field.

## Why it matters

In a stream, writers and readers are owned by different teams. The registry stops one team from breaking the others by mistake.

## Common mistake

Removing or renaming a field that readers still use. Set the registry to check that each change keeps old readers working.

## Three principles

- **One shared store.** Every event schema lives there.
- **ID in each event.** Readers look the schema up.
- **Compatibility checks.** Breaking changes are refused.

## Related terms

- [Event Streaming](https://learn.benibix.com/term/data/event-streaming)
- [Apache Kafka](https://learn.benibix.com/term/data/apache-kafka)
- [Apache Avro](https://learn.benibix.com/term/data/apache-avro)
- [Kafka Topic](https://learn.benibix.com/term/data/kafka-topic)
- [Confluent](https://learn.benibix.com/term/data/confluent)

---

Source: https://learn.benibix.com/term/data/schema-registry
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
