Defining a schema for events sent to an Apache Kafka® topic is essential to provide clarity to both producers and consumers regarding the contents of each event. This schema outlines the structure of the data format, which could be in various formats, including JSON, Avro, or Protobuf. A defined schema ensures smooth communication between producers and consumers.
Aiven's Karapace and Confluent's Schema Registry are two highly popular products that enable the management of schemas outside a Apache Kafka cluster. For more information, see Aiven Karapace and Confluent Schema registry.
Manage schema in Klaw
Schema management in Klaw is structured around the following:
- Klaw uses the concept of a Team for schema ownership and management, where the topic owner team requests a schema for a specific topic
- The team that owns the topic is responsible for making the final decision on any schema-related requests, such as approving or declining the request.
- For any requests related to a schema, the team that owns the topic is responsible for making the final decision, such as approving or declining the request.
- Klaw enforces the
TopicNameStrategystrategy to ensure only one schema is applied per topic, which uses the topic name to identify the schema subject used for schema lookups.
- Klaw supports Aiven's Karapace and Confluent Schema registry.