Pulsar Schema Registry
The Pulsar Schema Registry is a central repository to enable message producers and consumers on Pulsar topics to coordinate on the structure of topics for your message bus. The structure of the data, or its schema, may either be specified and uploaded through a REST interface or by the message producer itself. Each piece of data that is passed through the system is in turn stamped with the name and version of the schema it represents. With schemas for Avro and JSON, every single piece of data traveling through the system is completely discoverable, enabling to build systems that can easily adapt as the data changes.
Furthermore, the schema registry keeps track of data compatibility between versions of the schema. As new schemas are uploaded the registry ensures that new schema versions are able to be read by old consumers. This ensures that Producers are not able to break Consumers.
Hackolade supports Avro schema and JSON Schema maintenance in the Pulsar Schema Registry. Unlike many other Hackolade targets, this does not require a special plugin. It is done respectively through the Avro, Parquet or ProtoBuf plugins, or the JSON native target.
In effect, Hackolade provides a graphical interface for the design and maintenance of Avro and JSON schemas stored in Pulsar Schema Registry.
For the details on how to define Avro schema definitions in Hackolade, you should consult this Avro schema page.
Schemas for Avro or JSON defined in Hackolade can be added to subjects in the Schema Registry through an Apply button appearing at the bottom of the Avro Schema tab.
By pressing the button "Apply to instance" the system will automatically create a new version of the schema, if different from the latest one.
The reverse-engineering function lets you connect to the Pulsar Schema Registry, either on-prem or in the Cloud.
For more information, make sure to consult the Pulsar Schema Registry documentation.