SYSTEM Cited by 1 source
Confluent Schema Registry¶
Definition¶
Confluent Schema Registry is the widely-deployed
schema registry implementation in the Kafka
ecosystem, storing Avro/Protobuf/JSON Schema subjects, versions, and per-subject
compatibility settings and exposing them over a standard REST API. It backs its
state in an internal _schemas compacted Kafka topic and assigns a numeric
schema ID to each registered schema — the ID that Kafka serializers embed into
every record's wire format. It also offers a Contexts API
(contexts) for independent subject
namespaces within one registry, plus Confluent-specific extensions such as rule
sets, metadata tags, and compatibility groups.
It appears in this wiki primarily as a migration source: the registry teams are moving off when leaving Confluent (accelerated by the March 2026 IBM acquisition), replicated into Redpanda's built-in registry via API-mode Schema Registry replication.
Seen in¶
- sources/2026-08-25-redpanda-push-button-migration-from-confluent-to-redpanda-with-shadowing — as the migration source for Redpanda Shadowing 26.2. Its schema IDs, subject/version names, and per-subject compatibility modes are preserved on import; its registry-specific extensions (rule sets, metadata tags, compatibility groups) have "no Redpanda equivalent" and are skipped or stripped. Redpanda's registry is deliberately compatible with Confluent's Contexts API so context-using tooling keeps working after migration.
Related¶
- concepts/schema-registry — the general subsystem this implements.
- systems/kafka-schema-registry — the wiki's general Kafka-ecosystem registry page.
- concepts/schema-registry — the namespace feature Redpanda mirrors API-compatibly.
- concepts/schema-registry — how it is replicated into Redpanda.
- systems/redpanda-shadowing — the feature that migrates off it.
- systems/kafka — the streaming platform it serves.
- companies/redpanda — operator of the canonical migration instance.