How deeply does Kafka for Architects cover record name strategy?

Explains naming, independent evolution, polyglot topics, partition ordering, and REST lookup, but stops short of consumer implementation.

Record name strategy

As explained in Kafka for Architects

RecordNameStrategy is a Schema Registry subject-naming strategy that identifies subjects by fully qualified record name independently of Kafka topics.

RecordNameStrategy names a Schema Registry subject after an event’s fully qualified record name, such as com.example.ClientEvent, rather than after a Kafka topic. The schema lifecycle therefore remains independent of topic placement. section 6.4.3

This design supports polyglot topics containing multiple event types. ClientCreated, ClientUpdated, and ClientDeleted events can share a topic when their ordering matters, provided the client identifier is used as the partitioning key. section 6.4.3

Compared with topic-based subject naming, it provides:

Independent schema evolution: changes to one record subject do not automatically affect subjects associated with other topics or event types. section 6.4.3
Domain-oriented grouping: event types can be modeled independently of Kafka topic structure. section 6.4.3
Direct registry lookup through a subject such as com.example.ClientEvent-value and a requested version. section 6.4.3

Listing 6.10 An example of the client event in Avro format

{
  "type": "record",
  "name": "ClientEvent",
  "namespace": "com.example",
  "fields": [
    {
      "name": "eventId",
      "type": "string",
      "doc": "Unique identifier for the event"
    },
    {
      "name": "eventType",
      "type": "string",
      "doc": "Type of event (e.g., 'ClientCreated', 'ClientUpdated')"
    },
    {
      "name": "timestamp",
      "type": "long",
      "logicalType": "timestamp-millis",
      "doc": "Event timestamp in milliseconds"
    },
    {
      "name": "clientId",
      "type": "string",
      "doc": "Unique identifier for the client"
    },
    {
      "name": "clientName",
      "type": "string",
      "doc": "Name of the client"
    }
  ]
}

The Avro record defines the fully qualified name and fields used to derive the subject. section 6.4.3

How Kafka for Architects covers it

liveBook manning.com

Read Kafka for Architects on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Kafka Streams in Action, Second EditionRecordNameStrategy is a Schema Registry subject naming strategy that derives a schema subject from the fully qualified record name.

Compare how 2 books explain record name strategy →

Related concepts

subject name strategykind of · A subject name strategy is a rule that determines how Schema Registry subject names are derived and therefore where compatibility is checked.
topic record name strategycontrasts with · TopicRecordNameStrategy is a Schema Registry subject-naming strategy that derives subjects from a Kafka topic name and a record’s fully qualified name.
polyglot topicproduces · A polyglot topic is a Kafka topic that contains multiple event types with distinct schemas.
schema registryuses · A schema registry is a service that stores, versions, and provides schemas for structured data, often validating compatibility between schema versions.
strategykind of · A strategy is a planned approach for achieving objectives through coordinated choices, priorities, and actions.
topicuses · A topic is a named messaging destination or stream to which producers publish messages or records and from which consumers receive or read them.

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.