Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex MetaData Hub
    • About Yandex MetaData Hub
      • Schema registry
      • Content models and JSON schema evolution issues
      • Compatibility policies
    • Quotas and limits
  • Audit Trails events
  • Pricing policy
  • Troubleshooting
  • Public materials
  • Release notes

In this article:

  • Protobuf schema compatibility policies
  • JSON schema compatibility policies
  1. Concepts
  2. Schema Registry
  3. Compatibility policies

Compatibility policies

Written by
Yandex Cloud
Updated at March 28, 2025
  • Protobuf schema compatibility policies
  • JSON schema compatibility policies

A compatibility policy consists of rules Yandex Schema Registry uses to check the compatibility of the new schema with earlier versions at the namespace level.

You can select a compatibility policy when creating or updating the namespace. Compatibility policies are available for Protobuf and JSON Schema.

Protobuf schema compatibility policiesProtobuf schema compatibility policies

The following policies are available for Protobuf schemas:

  • Confluent: Based on the best practices for the evolution of Protobuf schemas. For more info on schema evolution, see this Protobuf guide.

  • buf: Based on the Buf v1 standards. For more info on the applicable checks, see this specification.

JSON schema compatibility policiesJSON schema compatibility policies

The following policies are available for JSON schemas:

  • Confluent: Follows the Confluent Schema Registry standards and implements mathematically accurate compatibility checks. This policy does not allow adding or removing optional parameters in object fields. In certain cases, such as when working with queues, this limitation may be excessive.

  • Optional Friendly: Based on a solution using various content models for the producer and the consumer. This option only involves registering the producer schema. The compatibility check involves converting the consumer schema from an open content model to a closed one and comparing it with the registered producer schemas. This enables you to add or remove optional parameters while maintaining full transitive compatibility.

Was the article helpful?

Previous
Content models and JSON schema evolution issues
Next
Quotas and limits
Yandex project
© 2025 Yandex.Cloud LLC