two-schema-registry-articles

Author: LHL407

articles/event-hubs/schema-registry-client-side-enforcement.md

@@ -1,5 +1,5 @@
 ---
-title: Client-side Schema Enforcement - Schema Registry
+title: Client-Side Schema Enforcement - Schema Registry
 description: This article provides information on using schemas in a schema registry when publishing or consuming events from Azure Event Hubs. 
 ms.topic: conceptual
 ms.date: 04/26/2023
@@ -11,9 +11,9 @@ ms.author: spelluru
 
 Client-side schema enforcement ensures that data is validated on the client side. The producer application sends the data and the consumer application receives it. That data is validated against schemas defined in the schema registry on the client side rather than the broker/server side.
 
-This flow is illustrated as shown:
+This diagram illustrates the flow:
 
-:::image type="content" source="./media/schema-registry-overview/information-flow.svg" alt-text="A diagram outlines the schema registry information flow." border="false":::
+:::image type="content" source="./media/schema-registry-overview/information-flow.svg" alt-text="Diagram that shows the schema registry information flow." border="false":::
 
 > [!NOTE]
 > The diagram showcases the information flow when event producers and consumers use a schema registry with the Kafka protocol and Avro schema. Other protocols and schema formats work in a similar way.
@@ -25,7 +25,7 @@ This flow is illustrated as shown:
 
 1. The serializer looks for the schema in the schema registry to serialize event data. If it finds the schema, then the corresponding schema ID is returned. You can configure the producer application to automatically register the schema with the schema registry if it doesn't exist.
 
-1. The serializer prepends the schema ID to the serialized data that is published to the Event Hubs.
+1. The serializer prepends the schema ID to the serialized data that's published to the event hub.
 
 ### Consumer
 

articles/event-hubs/schema-registry-concepts.md

@@ -7,37 +7,37 @@ author: spelluru
 ms.author: spelluru
 ---
 
-# Schema Registry in Azure Event Hubs
+# Schema registry concepts in Azure Event Hubs
 
 Schema registries in Azure Event Hubs have many benefits. They help 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 registries to achieve highly reliable data processing and governance with little operational overhead.
 
-Azure Event Hubs schema registries fulfill many roles in schema-driven, event-streaming scenarios:
+Azure Event Hubs schema registries fulfill many roles in schema-driven event-streaming scenarios:
 
-* They provide a repository where multiple schemas can be registered, managed, and evolved
-* They manage schema evolution with multiple compatibility rules
-* They perform data validation for all schematized data
-* They provide client-side libraries (serializers and deserializers) for producers and consumers
-* They improve network throughput efficiency by passing the schema ID instead of the schema definition for every payload
+* They provide a repository where multiple schemas can be registered, managed, and evolved.
+* They manage schema evolution with multiple compatibility rules.
+* They perform data validation for all schematized data.
+* They provide client-side libraries (serializers and deserializers) for producers and consumers.
+* They improve network throughput efficiency by passing the schema ID instead of the schema definition for every payload.
 
 Azure Event Hubs schema registries are supported on Standard, Premium, and Dedicated tiers.
 
 ## Schema registry components
 
-A schema registry lives in the context of the Event Hubs namespace, but can also be used with other message or events brokers, including Azure messaging services. It comprises multiple schema groups, which act as a logical grouping of schemas and can be managed independent of other schema groups.
+A schema registry lives in the context of the Event Hubs namespace but can also be used with other message or event brokers, including Azure messaging services. It comprises multiple schema groups, which act as a logical grouping of schemas and can be managed independently of other schema groups.
 
-:::image type="content" source="./media/schema-registry-overview/elements.png" alt-text="A diagram shows the components of a schema registry in Azure Event Hubs." border="false":::
+:::image type="content" source="./media/schema-registry-overview/elements.png" alt-text="Diagram that shows the components of a schema registry in Azure Event Hubs." border="false":::
 
 ### Schemas
 
-In any loosely coupled system, multiple applications communicate, primarily through data. Schemas define the structure of the data in a declarative way. As a result, the contract between producer and consumer applications is well-defined, ensuring reliable processing at scale.
+In any loosely coupled system, multiple applications communicate, primarily through data. Schemas define the structure of the data in a declarative way. As a result, the contract between producer and consumer applications is well defined, ensuring reliable processing at scale.
 
 A schema definition includes:
 
-* Fields: Individual data elements like name, book title, or address
-* Data types: The type of data that can be stored, like string, date-time, or array
-* Structure: How the fields are organized, like nested structures or arrays
+* Fields: Individual data elements like name, book title, or address.
+* Data types: The type of data that can be stored, like string, date-time, or array.
+* Structure: How the fields are organized, like nested structures or arrays.
 
-Schemas define the contract between producers and consumers. A schema defined in an Event Hubs schema registry helps manage the contract outside of event data, which removes the payload overhead.
+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.
 
 #### Schema formats
 
@@ -54,31 +54,29 @@ To learn more about using Avro schema format with an Event Hubs schema registry,
 
 ##### JSON schema
 
-[JSON (JavaScript Object Notation) schema](https://json-schema.org/) is a standardized way of defining the structure and data types of the events. JSON schema enables the confident and reliable use of the JSON data format in event streaming.
+A [JSON (JavaScript Object Notation) schema](https://json-schema.org/) is a standardized way of defining the structure and data types of the events. A JSON schema enables the confident and reliable use of the JSON data format in event streaming.
 
-To learn more about using the JSON schema format with an Event Hubs schema registry, see:
-  
-* [How to use a schema registry with Kafka and JSON schema](schema-registry-json-schema-kafka.md)
+To learn more about using the JSON schema format with an Event Hubs schema registry, see [How to use a schema registry with Kafka and JSON schema](schema-registry-json-schema-kafka.md).
 
 ##### Protocol Buffers
 
-[Protocol Buffers (Protobuf)](https://protobuf.dev/) is a language-neutral, platform-neutral, extensible mechanism for serializing structured data. It's used for efficiently defining data structures and serializing them into a compact, binary format.
+[Protocol Buffers (Protobuf)](https://protobuf.dev/) is a language-neutral, platform-neutral, extensible mechanism for serializing structured data. It's used for efficiently defining data structures and serializing them into a compact binary format.
 
 ### Schema groups
 
 Schema groups are logical groups of similar schemas that are organized according to your business criteria. A schema group holds:
 
-* Multiple schema definitions
-* Multiple versions of a specific schema
-* Metadata regarding the schema type and compatibility for all schemas in the group
+* Multiple schema definitions.
+* Multiple versions of a specific schema.
+* Metadata regarding the schema type and compatibility for all schemas in the group.
 
-You can think of a schema group as a subset of the schema registry that aligns with a particular application or organizational unit, with a separate authorization model. This extra security boundary ensures that metadata and trade secrets aren't leaked in the shared services model. It also allows application owners to manage schemas independent of other applications that share the same namespace.
+You can think of a schema group as a subset of the schema registry that aligns with a particular application or organizational unit, with a separate authorization model. This extra security boundary helps ensure that metadata and trade secrets aren't leaked in the shared services model. It also allows application owners to manage schemas independently of other applications that share the same namespace.
 
 ## Schema evolution
 
-Schemas need to evolve with the business requirement of producers and consumers. Azure schema registries support 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 in order for it to create a new version of the schema.
+Schemas need to evolve with the business requirement of producers and consumers. Azure schema registries support 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.
 
-Schema evolution is only supported for Avro schema format only.
+Schema evolution is supported for Avro schema format only.
 
 Azure Event Hubs schema registries are supported in the following compatibility modes.
 
@@ -102,15 +100,15 @@ When the ``None`` compatibility mode is used, the schema registry doesn't do any
 
 ## Client SDKs
 
-You can use one of the following libraries to include an Avro serializer. You can use Avro serializers to serialize and deserialize payloads containing schema registry schema identifiers and Avro-encoded data:
+You can use one of the following libraries to include an Avro serializer. You can use Avro serializers to serialize and deserialize payloads that contain schema registry schema identifiers and Avro-encoded data:
 
 * **.NET**: [Microsoft.Azure.Data.SchemaRegistry.ApacheAvro](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/schemaregistry/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro)
 * **Java**: [azure-data-schemaregistry-avro](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/schemaregistry/azure-data-schemaregistry-apacheavro)
 * **Python**: [azure-schemaregistry-avroserializer](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/schemaregistry/azure-schemaregistry-avroencoder/)
 * **JavaScript**: [@azure/schema-registry-avro](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/schemaregistry/schema-registry-avro)
-* **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 registries can be used in any Apache Kafka scenario and with any Apache Kafka-based deployment or cloud service.
-* **Azure CLI**: For an example of adding a schema to a schema group by using CLI, see [Adding a schema to a schema group using CLI](https://github.com/Azure/azure-event-hubs/tree/master/samples/Management/CLI/AddschematoSchemaGroups).
-* **PowerShell**: For an example of adding a schema to a schema group by using PowerShell, see [Adding a schema to a schema group using PowerShell](https://github.com/Azure/azure-event-hubs/tree/master/samples/Management/PowerShell/AddingSchematoSchemagroups).
+* **Apache Kafka**: Run [Kafka-integrated Avro](https://github.com/Azure/azure-schema-registry-for-kafka/) serializers and deserializers backed by Azure schema registries. The Java client's Apache Kafka® client serializer for Azure schema registries can be used in any Apache Kafka scenario and with any Apache Kafka-based deployment or cloud service.
+* **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).
+* **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).
 
 ## Limits
 
@@ -127,17 +125,17 @@ To access a schema registry programmatically, follow these steps:
 | ---- | ----------- |
 | Owner | Read, write, and delete schema registry groups and schemas |
 | Contributor | Read, write, and delete schema registry groups and schemas |
-| [Schema registry reader](../role-based-access-control/built-in-roles.md#schema-registry-reader-preview) | Read and list schema registry groups and schemas |
-| [Schema registry contributor](../role-based-access-control/built-in-roles.md#schema-registry-reader-preview) | Read, write, and delete schema registry groups and schemas |
+| [Schema Registry Reader](../role-based-access-control/built-in-roles.md#schema-registry-reader-preview) | Read and list schema registry groups and schemas |
+| [Schema Registry Contributor](../role-based-access-control/built-in-roles.md#schema-registry-reader-preview) | Read, write, and delete schema registry groups and schemas |
 
-To learn how to create and register an application using the Azure portal, see [Register an application with Microsoft Entra ID](../active-directory/develop/quickstart-register-app.md). You need the client ID (application ID), tenant ID, and the secret to use in the code.
+To learn how to create and register an application by using the Azure portal, see [Register an application with Microsoft Entra ID](../active-directory/develop/quickstart-register-app.md). You need the client ID (application ID), the tenant ID, and the secret to use in the code.
 
-## Next steps
+## Related content
 
-* To learn how to create a schema registry by using the Azure portal, see [Create an Event Hubs schema registry using the Azure portal](create-schema-registry.md).
+* To learn how to create a schema registry by using the Azure portal, see [Create an Event Hubs schema registry by using the Azure portal](create-schema-registry.md).
 * See the following **schema registry Avro client library** samples.
 * [.NET](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/schemaregistry/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro/tests/Samples)
 * [Java](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/schemaregistry/azure-data-schemaregistry-apacheavro/src/samples)
 * [JavaScript](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/schemaregistry/schema-registry-avro/samples)
 * [Python](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/schemaregistry/azure-schemaregistry-avroencoder/samples)
-* [Kafka Avro Integration for Azure Schema Registry](https://github.com/Azure/azure-schema-registry-for-kafka/tree/master/csharp/avro/samples)
+* [Kafka Avro Integration for Azure schema registries](https://github.com/Azure/azure-schema-registry-for-kafka/tree/master/csharp/avro/samples)