Data for Apache Kafkas
Kafka data handling is how records are encoded and how their structure is managed. Serialisers turn objects into bytes using formats such as JSON, Avro or Protobuf, and a schema registry stores versioned schemas and enforces compatibility rules so producers and consumers can evolve independently without breaking each other.
Stage: Design and Data · Part of the Apache Kafka roadmap · Last reviewed 19 November 2026
What to learn in Data
- Configure key and value serialisers and deserialisers in a client
- Compare JSON, Avro and Protobuf for event payloads
- Register a schema in a schema registry
- Apply backward or forward compatibility rules to a schema change
- Choose a message key that gives useful partitioning
Data interview questions
Why use a schema registry with Kafka?
Kafka stores only bytes, so nothing stops a producer changing a message format and breaking consumers. A schema registry stores versioned schemas, producers send a schema id with each message, and compatibility checks reject incompatible changes. This keeps data contracts explicit and safe to evolve.
What is the difference between backward and forward compatibility?
Backward compatible means consumers using the new schema can read data written with the old schema. Forward compatible means consumers on the old schema can read data written with the new one. Which you need depends on whether you upgrade consumers or producers first.
Where Data fits in the Apache Kafka roadmap
Data belongs to the Design and Data stage (intermediate level). Build pipelines.
Other units in this stage
Back to the full Apache Kafka roadmap