Adapt Frontend Apps for Schema Registry Manager

[AitorAlgorta]

Problem Description

Our application currently relies on a single Schema Registry provider, limiting our flexibility and scalability as we expand. Integrating with multiple Schema Registry providers is essential for accommodating diverse requirements and use cases.

Desired Solution

We propose adapting our frontend applications to support multiple Schema Registry providers efficiently. This adaptation involves using a new API dedicated to managing different providers, abstracting away provider-specific details for seamless integration.

Considered Alternatives

Current Approach: Continuing with the existing method of interfacing with a single Schema Registry provider. However, this approach lacks scalability and may lead to increased complexity.

Separate Modules: Developing separate modules for each Schema Registry provider to provide flexibility. However, this approach introduces code duplication and maintenance overhead.