Kafka for Developers - Data Contracts Using Schema Registry - Schema Registry Internals and Interacting with Schema Regi

This lecture provides an in-depth look at the internals of Schema Registry, focusing on how schemas are stored using Kafka topics and the various ways to interact with a running Schema Registry instance. It covers the use of RESTful services and tools like Insomnia to access API endpoints, manage schemas, and check compatibility. The lecture also introduces key resources such as subjects, schemas, config, and compatibility, and explains their roles in schema evolution and data contract enforcement.

Where does the Schema Registry store its schemas?

• In a cloud storage service

• In a local file system

• In an internal Kafka topic

• In a MySQL database

What is required for the Schema Registry to function properly?

• A REST client

• A Kafka Broker

• A cloud service

• A local server

Which tool can be used to interact with the Schema Registry's REST API?

• Microsoft Word

• Adobe Photoshop

• Google Chrome

• Insomnia

What is the purpose of the 'subjects' resource in the Schema Registry?

• To store user credentials

• To manage schema versions

• To configure network settings

• To provide different subjects for schema evolution

Which of the following is NOT a schema type supported by the Schema Registry?

• Avro

• JSON

• Protobuf

• XML

What is the primary use of the 'config' resource in the Schema Registry?

• To handle network traffic

• To manage cluster-level configurations

• To update user permissions

• To store schema data

What is the first step in using Insomnia to interact with the Schema Registry?

• Configure network settings

• Import the request collection

• Create a new schema

• Download the Kafka Broker