|
1 | 1 | ---
|
2 |
| -title: Azure Schema Registry in Event Hubs |
3 |
| -description: This article provides an overview of Schema Registry support by Azure Event Hubs. |
| 2 | +title: Azure Schema Registry in Event Hubs (preview) |
| 3 | +description: This article provides an overview of Schema Registry support by Azure Event Hubs (Preview). |
4 | 4 | ms.topic: overview
|
5 | 5 | ms.date: 05/10/2021
|
6 | 6 | ms.custom: references_regions
|
7 | 7 | ---
|
8 | 8 |
|
9 |
| -# Azure Schema Registry in Event Hubs |
| 9 | +# Azure Schema Registry in Event Hubs (Preview) |
10 | 10 | In many event streaming and messaging scenarios, the event or message payload contains structured data that's either being serialized or deserialized using a schema-driven format like Apache Avro. Both senders and receivers may want to validate the integrity of the data with a schema document as with JSON schema. For schema-driven formats, making the schema available to the message consumer is a prerequisite for the consumer to be able to deserialize the data.
|
11 | 11 |
|
12 | 12 | The **Azure Schema Registry** is a feature of Event Hubs, which provides a central repository for schema documents for event-driven and messaging-centric applications. It provides the flexibility for your producer and consumer applications to exchange data without having to manage and share the schema between them and also to evolve at different rates. The Schema Registry also provides a simple governance framework for reusable schemas and defines the relationship between schemas through a grouping construct (schema groups).
|
13 | 13 |
|
14 | 14 | > [!NOTE]
|
15 |
| -> The feature isn't available in the **basic** tier. |
| 15 | +> - The **Schema Registry** feature is currently in **preview**, and is not recommended for production workloads. |
| 16 | +> - The feature isn't available in the **basic** tier. |
16 | 17 |
|
17 | 18 | With schema-driven serialization frameworks like Apache Avro, externalizing serialization metadata into shared schemas can also help with dramatically reducing the per-message overhead of type information and field names included with every data set as it's the case with tagged formats such as JSON. Having schemas stored alongside the events and inside the eventing infrastructure ensures that the metadata required for serialization/de-serialization is always in reach and schemas can't be misplaced.
|
18 | 19 |
|
@@ -51,8 +52,8 @@ When accessing the schema registry programmatically, you need to register an app
|
51 | 52 | | ---- | ----------- |
|
52 | 53 | | Owner | Read, write, and delete Schema Registry groups and schemas. |
|
53 | 54 | | Contributor | Read, write, and delete Schema Registry groups and schemas. |
|
54 |
| -| [Schema Registry Reader](../role-based-access-control/built-in-roles.md#schema-registry-reader-preview) | Read and list Schema Registry groups and schemas. | |
55 |
| -| [Schema Registry Contributor](../role-based-access-control/built-in-roles.md#schema-registry-reader-preview) | Read, write, and delete Schema Registry groups and schemas. | |
| 55 | +| [Schema Registry Reader (Preview)](../role-based-access-control/built-in-roles.md#schema-registry-reader-preview) | Read and list Schema Registry groups and schemas. | |
| 56 | +| [Schema Registry Contributor (Preview)](../role-based-access-control/built-in-roles.md#schema-registry-reader-preview) | Read, write, and delete Schema Registry groups and schemas. | |
56 | 57 |
|
57 | 58 | For instructions on creating registering an application using the Azure portal, see [Register an app with Azure AD](../active-directory/develop/quickstart-register-app.md). Note down the client ID (application ID), tenant ID, and the secret to use in the code.
|
58 | 59 |
|
|
0 commit comments