Schema Registry for Cross-Client Data Model Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Challenges arise in sharing and validating data model definitions between servers and clients in full stack applications, leading to inconsistencies and errors due to differing versions or non-compliance with data model requirements.
Innovation Solution
A schema registry is implemented to aggregate data model definitions into a single file, providing a unified interface for consumer devices, with functions for accessing and validating data models, ensuring consistent usage and detecting errors at compile time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If data model definitions are shared between server and client, then consistency is improved, but version control and validation complexity increases
Solution Approach 1:
The patent introduces a schema registry as an intermediary component that stores and manages data model definitions. The registry acts as a centralized repository that both server and client can access to obtain validated schema definitions, eliminating the need for complex peer-to-peer validation logic and version synchronization mechanisms between the two ends.
Solution Approach 2:
The patent implements preliminary validation by registering data model schemas in advance with the schema registry before they are used in data access operations. This allows the system to validate data models proactively rather than reactively, catching inconsistencies early in the development process rather than during runtime execution.
2Reliability
If data models are validated on both server and client, then error detection is improved, but development time increases
Solution Approach 1:
The patent uses schema copying by registering data model definitions once in the schema registry and then reusing these registered schemas across multiple data access operations and both server and client implementations. This eliminates the need to reinvent validation logic for each use case and reduces redundant development work.
Solution Approach 2:
The schema registry provides universal validation functionality that serves both server-side and client-side data access operations. The same registered schemas are used to validate data models in different contexts and at different stages of the application lifecycle, reducing the need for separate validation mechanisms.
3Adaptability or versatility
If separate schema files are used for each data model, then flexibility is improved, but aggregation and management complexity increases
Solution Approach 1:
The patent merges multiple separate schema files into a unified schema registry structure. The registry consolidates scattered data model definitions into a centralized repository that can be accessed through a uniform interface, simplifying schema management while preserving the flexibility of individual schema definitions through the registration process.
Data Source
AI summary
In some embodiments, a method receives a schema registry in a file. The schema registry aggregates schema files for a data model that is associated with a database system used by servers and consumer devices. The schema files is in a first software language that describes objects in the data model, and the schema registry is in a second software language used by the consumer devices. A first function in the schema registry is executed for an object to retrieve an original schema for the object in the schema files to create first software code for the object with the original schema for an application that uses the data model. A second function in the schema registry is executed for the object to generate a new object from the original schema for the object to create second software code for a new object with the original schema for the application.