Writer and Reader Schema
Use the writer schema to interpret stored data and the reader schema to resolve fields, defaults, and promotions without hiding malformed records.
Use the writer schema to interpret stored data and the reader schema to resolve fields, defaults, and promotions without hiding malformed records.
Separate a registry subject, its version history, and schema IDs; choose a compatibility scope and retain the definitions needed for replay.
Choose a partition key for ordering and load distribution, keep its encoded form stable, and test what changes when keys or partition counts change.
Distinguish retained keyed state from full history, account for tombstone expiry, and avoid treating compaction as instant table replacement.
Understand how producer identity and sequences suppress protocol retries, and why a resubmitted business event still needs its own identity.
Read Kafka acknowledgment settings together with the in-sync replica set and minimum ISR, and distinguish acceptance from external completion.
Separate fetched position from durable progress, commit only completed prefixes, and interpret lag with retention and processing state.
Share Kafka partitions among group members, resume from committed progress, and handle unfinished work when ownership changes.
Understand Kafka’s ordering and parallelism boundary, distinguish partition offsets, and plan key placement before changing partition counts.