Confluent Platform 5.5 introduces long-awaited JSON Schema and Protobuf support in Confluent Schema Registry and across other platform components. 

Support for Protobuf and JSON Schema in Schema Registry provides the same assurances of data compatibility and consistency we already had with Avro, while opening up Kafka to more businesses, applications, and use cases that are built upon those data serialization formats. 

Tushar Thole (Engineering Leader, Confluent) and David Araujo (Product Manager, Confluent) share about these new improvements to Confluent Schema Registry, the differences between Apache Avro™, Protobuf, and JSON Schemas, how to treat optional fields, some of the arguments between Avro and Protobuf, and why it took some time for Schema Registry to support JSON Schemas and Protobuf.

Later, they talk about custom plugins, adding another layer of safety in Confluent Platform 5.5, and their vision for data governance.

EPISODE LINKS

• Introducing Confluent Platform 5.5
• Confluent Platform Now Supports Protobuf, JSON Schema, and Custom Formats
• Download Confluent Platform
• Getting Started with Protobuf in Confluent Cloud
• Read articles by Robert Yokota 
• Schema Validation with Confluent Platform 5.4 
• Playing Chess with Confluent Schema Registry
• JSON Schema specs
• Send feedback to [email protected]
• Fully managed Apache Kafka as a service! Try free.
• Join the Confluent Community Slack
• Learn more with Kafka tutorials, resources, and guides at Confluent Developer