advanced~3h
Schema Registry and Avro
Why raw JSON stops being safe once producers and consumers evolve independently, and how Avro plus a Schema Registry enforce a contract between them without a single shared deployment.
Learning objectives
- Beginner: Explain the specific failure mode where an unversioned JSON payload breaks a consumer after an independent producer deploy.
- Beginner: Describe what an Avro schema is and how it differs from a Java class or a JSON payload itself.
- Intermediate: Explain the Schema Registry's role as a shared source of truth for schema IDs, separate from the data plane.
- Intermediate: Register and evolve a schema using the Schema Registry's REST API.
- Advanced: Distinguish backward, forward, and full compatibility, and pick the correct one for a producer-evolves-first vs. consumer-evolves-first rollout.
- Advanced: Evolve a schema safely by adding an optional field with a default, and explain why removing a required field without a default breaks compatibility.
This is a Pro chapter
Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.
Schema Registry and Avro