Day 9 of 14 30 minJSON & AvroSchema RegistryCompatibility
Kafka only stores bytes, so producers and consumers must agree on what's inside. Compare JSON, Avro and Protobuf, use a schema registry to reject bad events, and evolve schemas safely with compatibility rules.
By the end of today you can
- Explain why Kafka needs serialisation and what serialisers do
- Compare JSON, Avro, Protobuf and JSON Schema
- Explain how a schema registry stores and checks schemas
- Evolve a schema safely using backward compatibility
- Read old and new events with the latest schema
What's inside
- 5 sections
- 3 diagrams and mind maps
- 4 code examples you can run
- 5-question quiz
- 1Kafka stores bytes
- 2Formats
- 3A schema registry
- 4Evolving a schema safely
- 5Real Kafka: Avro with Schema Registry
Sign in free to read this lesson
Get the full lesson with diagrams, runnable code and the quiz. Your progress is saved across devices.
Sign in free