You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-hubs/schema-registry-concepts.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Azure Schema Registry Concepts
3
-
description: This article explains concepts for using Azure Schema Registry in Azure Event Hubs.
2
+
title: Schema Registry in Azure Event Hubs
3
+
description: This article explains concepts for using Schema Registry in Azure Event Hubs.
4
4
ms.topic: conceptual
5
5
ms.date: 04/26/2023
6
6
author: spelluru
@@ -11,15 +11,15 @@ ms.author: spelluru
11
11
12
12
Schema Registry in Azure Event Hubs has many benefits. Schema Registry helps maintain data consistency, simplify schema evolution, enhance interoperability, and reduce development effort in loosely coupled and event-streaming workflows. Large distributed organizations that employ a centralized repository for schemas can use Schema Registry to achieve highly reliable data processing and governance with little operational overhead.
13
13
14
-
Azure Event Hubs Schema Registry fulfills many roles in schema-driven event-streaming scenarios:
14
+
Schema registries in Azure Event Hubs fulfill many roles in schema-driven event-streaming scenarios:
15
15
16
-
*Provides a repository where multiple schemas can be registered, managed, and evolved
17
-
*Manages schema evolution with multiple compatibility rules
18
-
*Performs data validation for all schematized data
19
-
*Provides client-side libraries (serializers and deserializers) for producers and consumers
20
-
*Improves network throughput efficiency by passing the schema ID instead of the schema definition for every payload
16
+
*Provide a repository where multiple schemas can be registered, managed, and evolved
17
+
*Manage schema evolution with multiple compatibility rules
18
+
*Perform data validation for all schematized data
19
+
*Provide client-side libraries (serializers and deserializers) for producers and consumers
20
+
*Improve network throughput efficiency by passing the schema ID instead of the schema definition for every payload
21
21
22
-
Azure Event Hubs Schema Registry is supported on Standard, Premium, and Dedicated tiers.
22
+
Schema registries in Azure Event Hubs are supported on Standard, Premium, and Dedicated tiers.
23
23
24
24
## Schema registry components
25
25
@@ -37,7 +37,7 @@ A schema definition includes:
37
37
* Data types: The type of data that can be stored, like string, date-time, or array.
38
38
* Structure: How the fields are organized, like nested structures or arrays.
39
39
40
-
Schemas define the contract between producers and consumers. A schema defined in an Event Hubs Schema Registry helps manage the contract outside event data, which removes the payload overhead.
40
+
Schemas define the contract between producers and consumers. A schema defined in an Event Hubs schema registry helps manage the contract outside event data, which removes the payload overhead.
41
41
42
42
#### Schema formats
43
43
@@ -74,11 +74,11 @@ You can think of a schema group as a subset of the schema registry that aligns w
74
74
75
75
## Schema evolution
76
76
77
-
Schemas need to evolve with the business requirement of producers and consumers. Azure Schema Registry supports schema evolution by introducing compatibility modes at the schema group level. When you create a schema group, you can specify the compatibility mode of the schemas that you include in that schema group. When you update a schema, the change needs to comply with the assigned compatibility mode so that it can create a new version of the schema.
77
+
Schemas need to evolve with the business requirement of producers and consumers. Schema Registry supports schema evolution by introducing compatibility modes at the schema group level. When you create a schema group, you can specify the compatibility mode of the schemas that you include in that schema group. When you update a schema, the change needs to comply with the assigned compatibility mode so that it can create a new version of the schema.
78
78
79
79
Schema evolution is supported for Avro schema format only.
80
80
81
-
Azure Event Hubs Schema Registry is supported in the following compatibility modes.
81
+
Schema Registry is supported in the following compatibility modes.
82
82
83
83
### Backward compatibility
84
84
@@ -106,7 +106,7 @@ You can use one of the following libraries to include an Avro serializer. You ca
***Apache Kafka**: Run [Kafka-integrated Avro](https://github.com/Azure/azure-schema-registry-for-kafka/) serializers and deserializers backed by Azure Schema Registry. The Java client's Apache Kafka client serializer for Azure Schema Registry can be used in any Apache Kafka scenario and with any Apache Kafka-based deployment or cloud service.
109
+
***Apache Kafka**: Run [Kafka-integrated Avro](https://github.com/Azure/azure-schema-registry-for-kafka/) serializers and deserializers backed by Azure Schema Registry. The Java client's Apache Kafka client serializer for Schema Registry can be used in any Apache Kafka scenario and with any Apache Kafka-based deployment or cloud service.
110
110
***Azure CLI**: For an example of adding a schema to a schema group by using the Azure CLI, see [Adding a schema to a schema group by using the Azure CLI](https://github.com/Azure/azure-event-hubs/tree/master/samples/Management/CLI/AddschematoSchemaGroups).
111
111
***PowerShell**: For an example of adding a schema to a schema group by using PowerShell, see [Adding a schema to a schema group by using PowerShell](https://github.com/Azure/azure-event-hubs/tree/master/samples/Management/PowerShell/AddingSchematoSchemagroups).
112
112
@@ -138,4 +138,4 @@ To learn how to create and register an application by using the Azure portal, se
0 commit comments