Cross Data Center Federation Service for Asset Collaboration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing enterprise software applications deployed across multiple data centers face challenges in enabling collaboration between customers onboarded at different data centers due to inadequate data availability and costly, inefficient multidirectional data copying.
Innovation Solution
A federation service is configured to replicate data across multiple data centers on an on-demand basis, allowing collaboration by determining the onboarding status of customers and replicating data assets as needed, while ensuring data availability and compliance with specified conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multidirectional data copying is implemented across multiple data centers, then data availability for collaboration is improved, but cost and operational complexity increase significantly
Solution Approach 1:
The patent merges multiple data center operations into a unified federation service that manages data replication across data centers. Instead of each data center independently copying data to all other data centers (multidirectional copying), the federation service consolidates replication logic, determining which data needs to be replicated to which data centers based on collaboration requests. This reduces operational complexity while maintaining data availability.
Solution Approach 2:
The federation service acts as an intermediary between customers at different data centers and the data replication process. It receives collaboration requests, determines the appropriate data centers involved, and orchestrates the selective replication of data assets. This intermediary approach eliminates the need for direct multidirectional copying between all data center pairs, reducing both cost and complexity.
2Adaptability or versatility
If data assets are replicated across all data centers, then collaboration between customers at different data centers is enabled, but unnecessary replication increases cost and resource consumption
Solution Approach 1:
The patent applies partial action by replicating data assets selectively rather than universally. The federation service evaluates each collaboration request and replicates only the specific data assets needed for that collaboration to the specific data centers where collaborating customers are located. This avoids the waste of replicating all data to all data centers, reducing resource consumption while enabling collaboration capability.
Solution Approach 2:
The system implements local quality by tailoring the data replication strategy to each specific collaboration scenario. Instead of a uniform replication approach, the federation service determines the appropriate data assets and destination data centers based on the specific collaboration request, customer locations, and existing data distribution. This localized approach optimizes resource usage for each collaboration instance.
3Loss of energy
If data federation service implements selective replication, then cost is reduced, but data integrity and consistency across data centers may be compromised
Solution Approach 1:
The federation service implements feedback mechanisms to monitor and maintain data integrity across data centers. When data assets are replicated selectively based on collaboration requests, the system tracks the replication status and can detect inconsistencies. The feedback loop ensures that data integrity constraints are verified and maintained, preventing corruption or loss of data consistency even with selective replication.
Solution Approach 2:
The system performs preliminary actions by establishing data integrity constraints and validation rules before replication occurs. The federation service evaluates data assets against integrity requirements prior to selective replication, ensuring that only valid, consistent data is replicated. This preliminary verification prevents propagation of inconsistent or corrupted data across data centers.
Data Source
AI summary
A method may include a collaboration controller receiving a collaboration request to share a data asset associated with a first customer onboarded at a first data center with a second customer. In response to the collaboration request, the collaboration controller may determine that the second customer is onboarded at a second data center but not the first customer. Moreover, the collaboration controller may replicate, at the second data center, the data asset associated with the first customer upon determining that a copy of the data asset is not already present at the second data center. The replicating of the data asset may provide the second customer access to the data asset by at least creating, at the second data center, the copy of the data asset. Related systems and computer program products are also provided.