Controller Bridge for Dynamic Runtime State Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in dynamically exchanging runtime state information between datacenters, especially during migration and federation, due to differences in control plane architectures and the complexity of handling dynamic state changes across multiple datacenters.
Innovation Solution
A controller bridge is introduced to facilitate the dynamic exchange of runtime state information, supporting both datacenter migration and federation, allowing for dynamic exchange with and without gateways, and accommodating various sharding approaches, including physical, logical, and combined sharding, without substantial modifications to existing architectures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If runtime state information is exchanged directly between control planes of multiple datacenters, then dynamic state exchange is achieved, but system complexity and difficulty of implementation increase significantly
Solution Approach 1:
A controller bridge is introduced as an intermediary component that connects to multiple control planes and facilitates runtime state information exchange between datacenters. The bridge abstracts the complexity of direct peer-to-peer communication, implementing state synchronization logic centrally while presenting simple interfaces to individual control planes. This mediator approach enables automated dynamic state exchange without requiring complex direct integration between all control plane pairs.
2Ease of operation
If control plane architecture is standardized across datacenters, then ease of operation is improved, but adaptability to different control plane implementations decreases
Solution Approach 1:
The controller bridge is designed with universal functionality to work with multiple different control plane architectures and implementations. It implements a standardized interface layer that can adapt to various control plane protocols and data formats, allowing the same bridge infrastructure to facilitate state exchange across heterogeneous datacenter environments without requiring standardization of the underlying control plane architectures.
3Ease of manufacture
If runtime state information is frozen during exchange, then implementation simplicity is improved, but loss of time and operational disruption increase
Solution Approach 1:
The controller bridge implements dynamic state exchange by continuously synchronizing runtime state information between control planes without freezing operations. It uses incremental update mechanisms that capture state changes in real-time and propagate them across datacenters, allowing continuous operation during migration or federation processes. This dynamic approach eliminates the need to freeze runtime state, preventing operational disruption while maintaining implementation feasibility through structured update protocols.
Data Source
AI summary
In an embodiment, a computer-implemented method for dynamically exchanging runtime state data between datacenters using a controller bridge is disclosed. In an embodiment, the method comprises: requesting, and receiving, one or more first runtime state data from one or more logical sharding central control planes (“CCPs”) controlling one or more logical sharding hosts; requesting, and receiving, one or more second runtime state data from one or more physical sharding CCPs controlling one or more physical sharding hosts; aggregating, to aggregated runtime state data, the one or more first runtime state data and the one or more second runtime state data; determining updated runtime state data based on the aggregated runtime state data, the one or more first runtime state data, and the one or more second runtime state data; and transmitting the updated runtime state data to the logical sharding CCPs and physical sharding CCPs.