-
Language:
English
-
Language:
English
Chapter 1. Introduction to Service Registry
This topic provides an overview of Service Registry features and explains the optional rules used to govern registry content:
Service Registry is a Technology Preview feature only. 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 using them in production.
These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview.
1.1. Service Registry overview
Service Registry is a datastore for standard event schemas and API designs. Service Registry enables enables you to decouple the structure of your data from your applications and to share and manage your data structure using a REST interface. For example, client applications can dynamically push/pull the latest schema updates to/from the registry at runtime without needing to redeploy.
Service Registry enables you to create optional rules to govern how registry content can evolve over time. For example, the available registry rule types include content validation and version compatibility. Service Registry also provides full Apache Kafka schema registry support, client serializer/deserializer (SerDe) to validate Kafka messages at runtime, and compatibility with existing Confluent Schema Registry clients.
Service Registry is built on the Apicurio Registry open source community project. For details, see https://github.com/apicurio/apicurio-registry.
1.1.1. Supported artifact types
Service Registry supports the following artifact types:
| Type | Description |
|---|---|
|
| Apache Avro schema |
|
| Google protocol buffers schema |
|
| JSON Schema |
|
| OpenAPI specification |
|
| AsyncAPI specification |
1.1.2. Storage implementations
Service Registry supports the following artifact storage implementations:
- Red Hat AMQ Streams 1.3
1.1.3. Available distributions
Service Registry distributions are available as follows:
| Distribution | Location |
|---|---|
| Container image | |
| Maven repository | |
| Full Maven repository (with all dependencies) | |
| Source code |
Both Maven repositories include a Kafka client serializer/deserializer implementation, which can be used by Kafka client developers to integrate with Service Registry. This implementation includes custom Serde Java classes, which enable Kafka client applications to push/pull their schemas from Service Registry at runtime.
You must have a subscription for Red Hat Fuse and be logged into the Red Hat Customer Portal to access the available Service Registry distributions.
1.1.4. Registry REST API
The Service 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
- Artifact versions
- Artifact metadata
- Global rules
- Artifact rules
For detailed information, see the Apicurio Registry REST API documentation.
Compatibility with Confluent Schema Registry
The Service Registry REST API is compatible with the Confluent Schema Registry REST API. This means that applications using Confluent client libraries can use Service Registry instead as a drop-in replacement. For more details, see Replacing Confluent Schema Registry with Red Hat Integration Service Registry.
1.1.5. Registry demo
Apicurio Registry provides an open source demo of Apache Avro serialization/deserialization based on storage in Apache Kafka Streams. This demo shows how the serializer/deserializer gets the Avro schema from the registry at runtime and then uses it to serialize and deserialize Kafka messages. For more details, see https://github.com/Apicurio/apicurio-registry-demo.
For another demo of Avro serialization/deserialization, this time with storage in an Apache Kafka cluster based on Strimzi, see the Red Hat Developer article on Getting Started with Red Hat Integration Service Registry.
1.2. Rules for registry content
To govern content evolution, you can configure optional rules for artifacts added to the registry, as a post-installation step. All rules configured for an artifact must pass before a new artifact version can be uploaded to the registry. The goal of these rules is to prevent invalid content from being added to the registry. For example, content can be invalid for the following reasons:
-
Invalid syntax for a given artifact type (for example,
AVROorPROTOBUF) - Valid syntax, but semantics violate company standards
- New content includes breaking changes to the current artifact version
1.2.1. When rules are applied
Rules are applied only when content is added to the registry. This includes the following REST operations:
- Creating an artifact
- Updating an artifact
- Creating an artifact version
If a rule is violated, Service Registry returns an HTTP error. The response body includes the violated rule and a message showing what went wrong.
If no rules are configured for an artifact, the set of currently configured global rules are applied.
1.2.2. How rules work
Each rule is simply a name and some optional configuration. The registry storage maintains the list of rules for each artifact and the list of global rules. Each rule in the list consists of a name and a set of configuration properties, which are specific to the rule implementation. For example, a validation rule might use a Map<String,String>, or a compatibility rule might use a single property of BACKWARD for compatibility with existing versions.
A rule is provided with the content of the current version of the artifact (if one exists) and the new version of the artifact being added. The rule implementation returns true or false depending on whether the artifact passes the rule. If not, the registry reports the reason why in an HTTP error response. Some rules might not use the previous version of the content. For example, compatibility rules use previous versions, but syntax or semantic validity rules do not.
1.2.3. Supported rule types
You can specify the following rule types to govern content evolution in the registry:
| Type | Description |
|---|---|
|
| Validates data before adding it to the registry. Includes the following values:
|
|
| Ensures that newly added artifacts are compatible with previously added versions. Includes the following values:
|
