Event-Driven Configuration Management for Service Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network computing environments face challenges in efficiently synchronizing configuration changes between service providers and consumers, leading to potential service outages due to outdated information or excessive resource usage from frequent polling.

Innovation Solution

A configuration management system that provides sequential and atomic configuration change data to service consumers, allowing them to update their local configuration state in the correct sequence, with the option to request a full snapshot of the current configuration state when errors or significant changes occur, and utilizes a scalable architecture with multiple cells to manage distribution and processing efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If frequent polling is used to synchronize configuration changes, then configuration information is kept up-to-date, but resource usage increases and service outages may occur

Engineering Contradiction:
Improveconfiguration information freshnessVSAvoidcomputing resource usage
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The system implements event-driven periodic action where configuration changes trigger notifications only when necessary, rather than continuous polling. The configuration management system detects configuration changes and sends notifications to consumer devices only when configuration state changes occur, eliminating the need for frequent periodic polling while maintaining information freshness.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system establishes a feedback mechanism where consumer devices register their interest in configuration changes and receive push notifications when changes occur. The configuration management system monitors configuration state and provides feedback to consumers automatically, creating an efficient closed-loop information synchronization system that reduces resource consumption compared to open-loop polling.

Inventive Principle:
Principle #23Feedback

2Reliability

If configuration changes are propagated quickly to all consumers, then service availability is maintained, but system complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidconfiguration management system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The configuration management system is segmented into modular components: a configuration management device that monitors and detects changes, notification components that communicate changes to consumers, and consumer devices that process updates. This segmentation allows the system to maintain reliability through distributed architecture while managing complexity through clear separation of concerns and standardized interfaces between components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Consumer devices perform preliminary actions by registering their interest in configuration changes before changes occur. The configuration management system maintains a registry of interested consumers and their subscription preferences. When configuration changes occur, the system efficiently targets notifications only to registered consumers, ensuring service availability while reducing unnecessary system complexity through pre-established communication channels.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If sequential configuration change data is provided to consumers, then synchronization accuracy is improved, but processing time increases

Engineering Contradiction:
Improveconfiguration synchronization accuracyVSAvoidconfiguration update processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The configuration management system performs preliminary actions by pre-processing and sequencing configuration change data before transmission to consumers. Configuration changes are captured, assigned sequence numbers, and organized in chronological order in advance. When consumers receive the data, they can efficiently process it sequentially without requiring complex real-time synchronization, thus maintaining accuracy while reducing processing time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of configuration change data with sequence information attached, allowing consumers to receive and process configurations in the correct sequence without blocking the configuration management system. Multiple consumers can simultaneously receive copies of the same configuration updates, maintaining synchronization accuracy through sequence numbers while enabling parallel processing that reduces overall system processing time.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10990385B1Streaming configuration management
Publication Date: 2021.04.27 AMAZON TECH INC
  • US10990385B1 patent drawing
  • US10990385B1 patent drawing
  • US10990385B1 patent drawing

AI summary

A scalable configuration management system manages distribution of data representing changes to configuration parameters in a network computing environment. The system uses a scalable pool of configuration management components to generate sequential update data for the configuration state of service providers, and distribute the sequential update data to service consumers. The service consumers can subscribe to and receive updates to the configuration state of service providers. In some embodiments, the system can provide snapshots of the complete current state of a service provider.