Schema registry
A schema registry is a service that stores, versions, and provides schemas for structured data, often validating compatibility between schema versions.
Kafka Streams in Action, Second Edition
Schema Registry is a service for storing and validating schemas so that serialized records remain compatible between producers and consumers.
- How it is used
- Enforces evolving event-data contracts between independently deployed Kafka producers and consumers.
- How deep it goes
- Explains registration, architecture, generated objects, compatibility, references, and client configuration; defers general producer and consumer details.
- Examples
- Uses Avenger schemas and generated Java objects, plus College, Company, Person, inventory, and user-activity schemas.
- What you can do after
- Operate/configure it by registering schemas, generating objects, selecting compatibility scope, and wiring Schema Registry-aware serializers, deserializers, or Serdes.
Read how Kafka Streams in Action, Second Edition explains schema registry →
Kafka for Architects
A schema registry is a service that centrally stores, versions, and validates schemas for structured data exchanged between producers and consumers.
- How it is used
- Provides a shared data contract for structured Kafka events exchanged by producers and consumers.
- How deep it goes
- Traces registration, schema IDs, client serialization, REST access, storage, and release choices, while treating validation as a client responsibility.
- Examples
- Uses a producer-to-consumer interaction diagram, REST requests, Avro client configuration, and automatic-versus-manual registration choices.
- What you can do after
- Operate/configure it by selecting registration controls, configuring format-aware clients, and planning migrations when compatibility rules are insufficient.
Apache Kafka in Action
A schema registry is a service that stores, versions, and provides access to schemas governing data formats.
- How it is used
- Centralizes Kafka schema storage, versioning, compatibility checks, and access for producers and consumers.
- How deep it goes
- Explains registry functions, Avro schema-ID messaging, and operational risks, but leaves client-side enforcement mitigation unspecified.
- Examples
- Uses a Product Avro record and contrasts sending its full schema with referencing it by ID.
- What you can do after
- Apply schema IDs to Kafka messages while keeping schemas centrally stored and compatibility-checked.
Related concepts
- RESTuses · REST is an architectural style for distributed hypermedia systems that organizes interactions around resources and representations through constraints including a uniform interface, stateless communication, cacheability, and layered components.
- Gradle pluginused by · A Gradle plugin is an extension that adds project configuration, tasks, or integrations to the Gradle build system.
- backward compatibilityuses · Backward compatibility is the property of a changed or newer system remaining usable by existing clients and consumers of its earlier interfaces, behavior, or data.
- schemauses · A data schema is a formal specification of the structure, fields, types, relationships, and constraints of data.
- Avrouses · Apache Avro is a language-independent data serialization system that uses schemas to encode structured data, commonly in compact binary or JSON form.
- Apache Kafkauses · Apache Kafka is a distributed event-streaming platform for publishing, storing, processing, and consuming streams of records.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.