Chapter 5. Service Registry
Service Registry is available as a Technology Preview feature in Red Hat Integration 2019-12. Service Registry is a datastore for standard event schemas and API designs that is based on the Apicurio Registry open source community project. Service Registry enables developers to manage and share the structure of their data using a REST interface. For example, client applications can dynamically push/pull the latest updates to/from the registry without needing to redeploy.
Service Registry also enables developers to create rules to govern how registry content can evolve over time. For example, this includes rules for content validation and version compatibility.
Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend implementing any Technology Preview features in production environments. This Technology Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about support scope, see Technology Preview Features Support Scope.
5.1. Supported artifact types Copy linkLink copied to clipboard!
Service Registry supports the following artifact types:
- Apache Avro schema
- Google Protocol buffers (Protobuf) schema
- JSON Schema
- OpenAPI specification
- AsyncAPI specification
5.2. Service Registry REST API Copy linkLink copied to clipboard!
The Registry REST API enables client applications to manage the artifacts in the registry. It provides create, read, update, and delete operations for the following:
- Schema and API artifacts
- Versions
- Metadata
- Global and artifact rules
The Registry REST API is also compatible with the Confluent Schema Registry REST API. This means that applications using Confluent client libraries can use Service Registry instead.
Additional resources