Schema Registry Component Architecture
The following diagram represents the component architecture of Schema Registry.
Schema Registry has three main components:
Registry web server
A web application that exposes the REST endpoints you can use to manage schema entities. You can use a web proxy and load balancer with multiple Web Servers to achieve HA and scalability.
Pluggable storage
Schema Registry uses the following two types of storages:
Schema Metadata Storage
A relational store that holds the metadata for the schema entities. Supports both in-memory storage (for development purposes) and mySQL databases.
Serdes Storage
File storage for the serializer and deserializer jars. Supports local file system (default) and HDFS storage.
Schema Registry client
A Java client that HDF components can use to interact with the RESTful services.
There are three integration points with HDF:
Custom NiFi processors
New processors and controller services in NiFi that interact with the Schema Registry.
Kafka serializer and deserializer
A Kafka serializer and deserializer that uses Schema Registry. The Kafka serdes can be found on GitHub.
Hortonworks Streaming Analytics Manager processors