API Schema Proxy Objects for Zero-Downtime Database Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
During database maintenance procedures like upgrades, changing the schema for a large number of users is difficult and can result in errors, as direct consumers require individual updates to connection information, which is time-consuming and resource-intensive.
Innovation Solution
Implementing an API-schema with proxy objects that map to access schemas, allowing for a stable database schema and user access even during schema modifications, enabling zero-downtime upgrades by maintaining a static API-schema name and redirecting synonym objects to new access schemas.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new schema is created during maintenance procedures, then the application can access updated data structures, but direct consumers cannot easily connect to the new schema and errors occur
Solution Approach 1:
The patent introduces an intermediary layer (API schema with proxy objects) between direct consumers and the underlying access schemas. This intermediary automatically redirects consumers to the appropriate schema version based on the object type, eliminating the need for consumers to manually update connection information when schemas change during maintenance procedures.
Solution Approach 2:
The patent segments the schema management into multiple independent access schemas (first access schema, second access schema) with a unified API schema layer. This segmentation allows different schema versions to coexist and be managed independently while presenting a unified interface to consumers, enabling smooth transitions during maintenance.
2Reliability
If individual user connection information is updated for each direct consumer, then accurate schema access is achieved, but the process becomes time-consuming and resource-intensive
Solution Approach 1:
The API schema with proxy objects provides self-service functionality by automatically determining the correct target schema and redirecting consumers without manual intervention. The system autonomously manages schema versioning and consumer redirection, eliminating the time-consuming manual update process while maintaining reliable schema access.
Solution Approach 2:
The intermediary API schema layer automatically manages the complexity of schema versioning and consumer redirection, shielding direct consumers from the need to manually update connection information. This intermediary handles schema resolution transparently, maintaining both accuracy and efficiency.
3Adaptability or versatility
If the API-schema mapping is revised to map to the second access schema, then the second version of the application can access data correctly, but the first version loses access to the original schema
Solution Approach 1:
The patent implements dynamic schema mapping where the API schema can adapt its mappings based on the application version and object type. The mapping configuration can be dynamically adjusted to support multiple application versions simultaneously, allowing the system to transition from supporting only the first version to supporting both first and second versions without loss of access.
Solution Approach 2:
The API schema is designed with universal mapping capabilities that can reference multiple access schemas simultaneously. This multi-functionality allows a single API schema to serve both first and second version applications by routing requests to the appropriate underlying schema based on the specific object and application version requirements.
Data Source
AI summary
Implementations for data migration in a maintenance procedure executed on a software system include actions of providing a first access schema, through which a first version of an application accesses data in a database system, establishing an API-schema, through which at least one direct consumer accesses data in the database system, the API-schema including one or more proxy objects that are mapped to respective one or more objects of the first access schema based on metadata of the API-schema, the metadata providing a mapping and one or more object definitions, and in response to execution of a maintenance procedure: providing a second access schema, through which a second version of the application accesses data in the database system, switching to the second access schema, and revising the mapping of the API-schema, such that at least one proxy object of the API-schema maps to a respective object of the second access schema.