Schema Registry
Confluent Schema Registry
Judgement: Adopt
The default Kafka schema-management surface.
A central registry for the schemas of messages flowing through Kafka topics. Producers register Avro, JSON Schema, or Protobuf schemas; consumers fetch them by ID to deserialise safely. Without it, "what shape is this Kafka topic?" has no answer.
The REST API was designed by Confluent but the protocol is widely re-implemented: Apicurio Registry (Red Hat), AWS Glue Schema Registry, Karapace (Aiven), and Redpanda Schema Registry all speak it. That makes it the de-facto schema catalog of the streaming world, even if it is not formally standardised.
Why it counts as a standard
Confluent's Schema Registry REST API is publicly documented and re-implemented by Apicurio (Red Hat), AWS Glue, Karapace (Aiven), and Redpanda. Producers and consumers depend on the API contract, not on Confluent's server — which is what promotes it from a vendor product to a de-facto standard.
At a glance
- Category
- Catalog APIs
- Governance
- Confluent (open API; multiple compatible implementations)
- Status
- De-facto standard for streaming schemas
- First released
- 2014
Links
Related standards
Other standards in Catalog APIs.
- Iceberg Catalog — Iceberg REST Catalog
- Unity Catalog
- DuckLake
- Hive Metastore — Apache Hive Metastore
See Schema Registry in context
Open the interactive Data Landscape to compare Schema Registry against every other open standard, or grab the raw JSON. Spotted something wrong? Open an issue.