Every consumer breaks without a Kafka Schema Registry check

A field type changed in last week's release, and three downstream consumers threw parsing errors at 2am.

Intermediate to advancedRead 6 minDoing: an afternoon7 steps

▶ Start

What you'll have at the end

A registered Avro schema with backward compatibility enforced, proven by a rejected incompatible schema change

Before you start

You need

A Kafka topic already carrying real producer traffic, with more than one consumer reading it, and admin access to add a schema check in front of it.

Not covered

Migrating a change that genuinely needs to break compatibility: that takes a new topic and a planned cutover, work this recipe leaves alone.

Leans on

7 steps

Where to go next

One bad Kafka message stalls a partition with no dead-letter topic

for when a message that violates the shape still lands on the topic anyway and a consumer needs to set it aside instead of crashing on everything behind it.

Checked 26 Aug 2026

Part of the Apache Kafka cookbook