Externalized Configuration Caching for Runtime Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional HR system management is inefficient in dynamically changing application configurations at run-time, requiring code deployment across all application containers, which incurs unnecessary testing, downtime, and processing costs for configuration changes when no application logic is changing.
Innovation Solution
The method involves using a shared cache to store configuration version data in a structured format, with API calls for managing configuration versions, and local caching to translate and store data in a run-time format, allowing for quick changes to container and application configurations without code deployment, utilizing Redis and MongoDB for data storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If code deployment is used to change configuration across all application containers, then configuration consistency is maintained, but deployment time and processing costs increase
Solution Approach 1:
The patent segments configuration management from application code deployment by introducing a separate configuration service that independently manages and distributes configuration data to containers, allowing configuration changes without full code deployment
Solution Approach 2:
The patent introduces a configuration service as an intermediary component that sits between the configuration source and application containers, handling configuration distribution and caching to eliminate the need for direct code deployment for configuration changes
2Reliability
If configuration changes are propagated to all application containers, then system-wide consistency is achieved, but unnecessary processing costs are incurred when no application logic is changing
Solution Approach 1:
The patent implements local caching of configuration data in each container and in the configuration service, allowing containers to use locally cached configurations when no changes are needed, thereby reducing unnecessary processing and energy consumption while maintaining consistency when changes occur
Solution Approach 2:
The patent implements a feedback mechanism where the configuration service monitors for actual configuration changes and only propagates updates when changes are detected, preventing unnecessary processing costs associated with propagating unchanged configurations
3Reliability
If configuration data is stored in structured format in shared cache, then data integrity is maintained, but run-time execution performance is reduced without translation
Solution Approach 1:
The patent performs preliminary translation of configuration data from structured format to run-time format and stores the translated version in advance in the configuration service cache, so that during run-time, containers can directly use the pre-translated data without real-time translation overhead, thus improving execution performance while maintaining data integrity
Data Source
AI summary
Aspects store configuration version data for an application into a shared cache in a structured data format; in response to a request at run-time for the configuration version data, determine whether run-time format data of the configuration version data is stored in a different, local cache; and in response to determining that the run-time format configuration version data is not stored in the local cache, during execution of the application, read the structured data format data from the shared cache, translate the read data into the run-time data format, store the translated data into the local cache in the run-time format file and return the configuration version run-time format data stored within the local cache in satisfaction of the request at run-time for the configuration version data of the application.