Centralized Configuration for Distributed System Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Managing multiple local application configurations in a distributed system is time-consuming and error-prone due to the need for manual updates, which can result in significant downtime and difficulties in onboarding new customers or dealers with unique configurations.

Innovation Solution

Implementing a centralized configuration system that allows for efficient updates and management of local application configurations by broadcasting or polling changes, reducing the need for complete rewrites and ensuring consistency across similar applications, while also serving as an API for new applications to streamline configuration management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual updates are used for each local application configuration, then configuration accuracy can be maintained, but time consumption increases and errors occur

Engineering Contradiction:

Improveconfiguration accuracyVSAvoidupdate time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a centralized configuration that serves as a master copy for multiple local application configurations. Instead of manually updating each local configuration individually, the system copies the centralized configuration to all relevant local systems, significantly reducing update time while maintaining accuracy through a single source of truth.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent merges multiple separate configuration management operations into a single centralized configuration system. By combining all local configuration updates into one centralized management point, the system eliminates the time-consuming manual update process for each individual local application while ensuring consistency across all configurations.

Inventive Principle:

Principle #5Merging (Combining)

2Reliability

If complete rewrite of local application configuration is performed, then configuration consistency is achieved, but system downtime increases

Engineering Contradiction:

Improveconfiguration consistencyVSAvoidsystem downtime

Core Design Contradiction:

ReliabilityVSDuration of action of moving object

Solution Approach 1:

The system uses a centralized configuration that can be copied to local systems without requiring complete rewrites. When updates are needed, the centralized configuration is copied to relevant local applications, allowing changes to take effect without shutting down systems or performing complete configuration rewrites, thus minimizing downtime.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The centralized configuration is prepared and validated in advance before being deployed to local systems. This preliminary action ensures that configurations are ready to be applied smoothly without requiring disruptive complete rewrites at the time of deployment, reducing system downtime.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If unique local application configurations are created for each customer, then customization is achieved, but onboarding complexity increases

Engineering Contradiction:

Improveconfiguration customizationVSAvoidonboarding complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system allows each local application configuration to have its own unique settings tailored to specific customer needs while still drawing from a common centralized configuration framework. This enables customization for each customer without requiring complete reconfiguration from scratch, simplifying the onboarding process.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

During onboarding, new customer configurations are created by copying the centralized configuration template and then customizing the relevant portions. This approach significantly reduces onboarding complexity compared to creating configurations from scratch, as the bulk of the configuration structure is already in place and can be reused.

Inventive Principle:

Principle #26Copying

4Productivity

If centralized configuration is implemented, then update efficiency is improved, but system architecture complexity increases

Engineering Contradiction:

Improveupdate efficiencyVSAvoidsystem architecture

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The centralized configuration acts as an intermediary between configuration management and local application systems. This intermediary layer handles the complexity of synchronization, copying, and configuration distribution, allowing local systems to remain relatively simple while achieving efficient centralized updates.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20230344710A1Centralized configuration for a distributed system

Publication Date: 2023.10.26 CDK GLOBAL LLC

AI summary

Embodiments herein relate to managing a distributed system with various local configurations using one or more centralized configurations. A central configuration system may store one or more centralized configurations for a set of applications. Updates to the centralized configurations may be transmitted to one or more of a plurality of local systems. The plurality of local systems may execute one or more of the set of applications. Each application may be associated with a local application configuration specific to a local system on which the application is executed. The local systems may determine whether the updates to the centralized configurations apply to the local application configuration for the one or more local applications stored on the memory, and update the local application configuration when the updates are applicable.