Centralized Configuration Database Cache Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As a federation of electronic systems grows by scaling out, the centralized manager faces inefficiencies in collecting and synchronizing information from independent clusters or cluster groups, leading to slow management responses due to distributed queries and the need for parsing and converting query results.
Innovation Solution
An aggregator selects nodes to synchronize configuration database information, receiving transaction log information in the form of database statements and playing it back into a centralized configuration database cache without parsing or conversion, using triggers to transmit only changes, thus maintaining fast and efficient synchronization across independent clusters or cluster groups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If distributed queries are used to collect information from independent clusters, then the system can scale out to more clusters, but the management response speed deteriorates due to the need to parse and convert query results
Solution Approach 1:
The patent applies preliminary action by pre-establishing event channels between the aggregator and cluster management modules before any configuration changes occur. These channels are set up in advance to receive transaction log information directly from the database triggers, eliminating the need for subsequent parsing and conversion operations. This pre-configured event-driven architecture enables the system to scale to multiple clusters while maintaining fast response speeds.
2Reliability
If centralized management is implemented across multiple clusters, then information synchronization can be achieved, but the complexity of collecting and synchronizing information from independent clusters increases
Solution Approach 1:
The patent introduces an event channel as an intermediary component between the distributed cluster management modules and the centralized aggregator. This intermediary receives transaction log information directly from database triggers via standardized event channels, simplifying the synchronization process. The event channel acts as a mediator that handles the complexity of information collection and transmission, allowing the aggregator to receive pre-processed data without implementing complex collection logic.
3Productivity
If transaction log information is transmitted with triggers, then only changes are sent improving efficiency, but the need for event channel setup and maintenance adds system complexity
Solution Approach 1:
The patent implements self-service by enabling the database management module to automatically generate and transmit transaction log information through event channels when configuration changes occur. The database triggers automatically detect changes and push information to the aggregator without requiring manual intervention or complex management protocols. This self-service mechanism maintains high synchronization efficiency while reducing the operational complexity of event channel management.
Data Source
AI summary
Example implementations relate to synchronizing configuration dataset information from independent cluster groups. In an example, an aggregator selects nodes to each represent a different respective cluster group of a plurality of independent cluster groups. The aggregator establishes a respective server-sent event channel with each of the nodes. The aggregator receives, from a node, transaction log information representing changes to a configuration database associated with the independent cluster group represented by the node. The aggregator plays back the received transaction log information, which is in the form of database statements, into a centralized configuration database cache.