Host Platform Configuration Repository for Microservices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a microservices architecture, managing consistent configuration across multiple independent services is complex, especially when updates are needed, as each service requires individual configuration updates, which can be time-consuming and complicated by interactions with different systems like databases and cloud environments.
Innovation Solution
A configuration repository on a host platform, such as a cloud platform, manages configuration for applications and microservices by extracting and synchronizing configuration content from a central system, creating a mapping to preserve links between applications and services, and distributing updated configuration content across various systems, ensuring consistency across all systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a microservices architecture is used to enable independent deployment and scaling of services, then adaptability and productivity are improved, but device complexity and difficulty of configuration management increase
Solution Approach 1:
The patent segments configuration management into two distinct layers: a central configuration system that stores and manages master configuration data, and local configuration instances in each microservice that consume this data. This segmentation allows independent service deployment while maintaining centralized configuration control, resolving the contradiction between microservice independence and configuration management complexity.
Solution Approach 2:
The patent introduces a configuration consumption mechanism as an intermediary between the central configuration system and microservices. This intermediary automatically retrieves and applies configuration data, eliminating the need for manual configuration updates in each service and reducing configuration management complexity while preserving service independence.
2Stability of the object's composition
If configuration data is stored in a central system for microservices, then configuration consistency is improved, but the time and complexity of propagating updates across all services increases
Solution Approach 1:
The patent implements preliminary action by having microservices automatically retrieve and cache configuration data from the central system during service startup or before configuration is needed. This preliminary retrieval eliminates the need for real-time propagation during updates, maintaining configuration consistency while reducing update time through asynchronous configuration consumption.
Solution Approach 2:
The patent enables continuous configuration consumption where microservices can dynamically retrieve updated configuration data from the central system without requiring service restart or manual intervention. This continuous action ensures configuration consistency is maintained across all services while minimizing disruption and update time.
3Adaptability or versatility
If manual configuration updates are performed on each microservice individually, then service independence is maintained, but productivity and ease of operation deteriorate
Solution Approach 1:
The patent implements self-service by enabling microservices to automatically consume and apply configuration data from the central configuration system without manual intervention. Each service independently retrieves its own configuration, maintaining service independence while dramatically improving configuration update efficiency through automated configuration consumption.
Data Source
AI summary
Provided is a system and method in which configuration content from central system is repackaged and distributed to applications on a host platform. In one example, the method may include receiving, via a host platform, configuration content from a central system, the configuration content comprising one or more configuration objects of a tenant, identifying an application of the tenant on the host platform which uses the one or more configuration objects based on a configuration object to application mapping, and distributing the one or more configuration objects to the identified application of the tenant on the host platform.