Hybrid Cloud Version Management via Tenant Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional hybrid cloud systems face challenges in version management due to inconsistent version update rhythms of application programming interfaces (APIs) across tenants, leading to difficulties in system-wide version updates and affecting iteration speed.
Innovation Solution
A version management system and method that includes a cloud server with a cloud version update module, configuration repository, and cloud configuration management module, and a local server with a local version update module, enabling automatic version management by publishing configuration data and updating version correspondence tables to ensure consistent version execution across cloud and local APIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If the cloud application programming interface is updated to a new version, then the cloud server can provide new functions, but the local application programming interfaces of tenants with inconsistent version update rhythms cannot cooperate, causing the new version functions to be unavailable
Solution Approach 1:
The system segments version management by tenant, allowing each tenant's local application programming interface to maintain its own version independently. The cloud server divides configuration data into tenant-specific segments, enabling selective version updates without requiring all tenants to update simultaneously. This segmentation resolves the contradiction by allowing the cloud to iterate versions quickly while maintaining compatibility with each tenant's current version through dedicated configuration segments.
Solution Approach 2:
The patent introduces configuration data as an intermediary layer between the cloud application programming interface and local application programming interfaces. This configuration data contains version correspondence relationships that mediate the interaction between different versions. When the cloud API is updated, the configuration data is updated to map the new cloud version with compatible local versions, allowing new functions to be available while maintaining compatibility with tenants at different version stages.
2Reliability
If all local systems must complete version update before the overall system is considered updated, then version compatibility is maintained, but the version update process becomes slow and affects productivity
Solution Approach 1:
The system performs preliminary actions by pre-configuring version correspondence relationships in the configuration data before actual version updates occur. The cloud server prepares multiple version mapping configurations in advance, allowing it to quickly switch between different version combinations without requiring coordinated updates across all tenants. This preliminary configuration enables the overall system to be considered updated as soon as the cloud server completes its update, rather than waiting for all local systems.
Solution Approach 2:
The version correspondence table is designed to be dynamic and adaptable, allowing the cloud server to adjust version mappings in real-time based on which tenants have updated their local application programming interfaces. This dynamic configuration enables the system to maintain compatibility while allowing different tenants to progress through version updates at different paces, significantly improving version update efficiency without sacrificing compatibility.
3Adaptability or versatility
If the cloud application programming interface version is updated without restrictions, then cloud service flexibility is improved, but management difficulty of the overall hybrid cloud system increases
Solution Approach 1:
The configuration data structure is designed with universal applicability, serving multiple functions simultaneously: it stores version correspondence relationships, manages tenant-specific configurations, and provides a unified interface for version management operations. This multi-functional configuration system allows the cloud server to update versions freely while automatically managing compatibility, reducing the perceived management complexity despite the flexibility gained.
Solution Approach 2:
The system implements feedback mechanisms where the cloud server monitors the version status of local application programming interfaces and automatically adjusts version correspondence configurations accordingly. This feedback loop allows unrestricted cloud version updates while automatically maintaining system-wide compatibility, as the configuration data is dynamically updated based on feedback from tenant version statuses, thereby reducing management complexity through automation.
Data Source
AI summary
A version management system and method are provided. The version management system includes a cloud server and a local server. When a first cloud application programming interface of a first local application programming interface corresponding to a first tenant is updated from a first version to a second version, a cloud version update module publishes first configuration data to be version updated to a configuration repository. When the cloud version update module judges that the first local application programming interface is updated from the first version to the second version through a local version update module, the cloud version update module updates a cloud version correspondence table. When the cloud server calls the first cloud application programming interface, a cloud configuration management module loads the first configuration data to be version updated, so that the cloud server executes the second version of the first cloud application programming interface.