liveBook · Manning

Topic name strategy

As explained in Kafka for Architects

TopicNameStrategy is a Schema Registry subject-naming strategy that groups schema versions by Kafka topic and message component.

TopicNameStrategy is Schema Registry’s default subject-naming strategy. It evolves a subject within one Kafka topic, grouping that topic’s compatible schema versions under a topic-derived name. section 6.4.3

For a CLIENTS topic, value schemas use the subject CLIENTS-value; key schemas can use CLIENTS-key. Registering the same schema for PERSONS creates a separate PERSONS-value subject. section 6.4.3

Client event on CLIENTS

A ClientEvent Avro schema published to CLIENTS is registered under CLIENTS-value. Its versions can be retrieved through the Schema Registry REST API using the subject and version number. section 6.4.3

How Kafka for Architects covers it

How deep it goes
Defines subject naming, value and key conventions, cross-topic separation, and REST version addressing.
Examples
Uses ClientEvent on CLIENTS with CLIENTS-value and contrasts registration on PERSONS with PERSONS-value.
What you can do after
Evaluate topic-scoped schema registration and retrieve a specific schema version through the Schema Registry REST API.
How it connects
Connects Kafka topics, Schema Registry subjects, schema evolution, message keys, message values, and Avro schemas.

Also explained in

Compare how 2 books explain topic name strategy →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kafka for Architects. The section links point to the parts of the book it draws on.