Populating a central schema registry

We’ve just seen how, by having our schemas accessible to our code, we can make use of a variety of libraries to ease the generation and consumption of data. That relies on having easy access to those schemas, wherever you need them. In this section, we’ll learn how to populate a schema registry from our data contract, making our schemas available to any service or code, at any time.

Again, we’ll be converting our data contract to JSON Schema, then using that to populate the schema registry, as highlighted in the following diagram:

Figure 8.6 – Converting the data contract to JSON Schema to populate a schema registry

We discussed schema registries and their benefits in Chapter 6, What Makes Up a Data Contract, under the Using a schema registry as the source of truth section. One of the benefits we mentioned is that they act as a central store for the schemas, so any application can access...