Configuration Hash Comparison for Microservice Settings
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In microservice architectures, systems face challenges in efficiently managing and comparing settings across multiple APIs, leading to inefficiencies and duplication of efforts, especially when handling large volumes of API requests, which hinders optimal data processing and troubleshooting.
Innovation Solution
A distributed API gateway architecture is implemented, where common functionalities are bundled into gateway nodes, allowing for centralized management and plugin-based extensions, enabling efficient scaling and reduced complexity by sharing data stores and plugin configurations across nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If microservices are monitored individually across distributed systems, then system autonomy and scalability are improved, but settings management complexity and duplication increase
Solution Approach 1:
The patent combines scattered microservice settings into a unified hierarchical structure organized by business domains. Settings that were previously distributed across multiple independent microservices are now centralized in a single configuration system that maintains the ability to propagate changes across the entire system or specific subsets of services.
Solution Approach 2:
The configuration system serves multiple functions: it acts as a centralized repository for all microservice settings, a propagation mechanism for distributing configuration changes, a validation system for ensuring setting correctness, and a domain-oriented organization structure. This multi-functional approach replaces multiple separate settings management systems.
2Stability of the object's composition
If configuration changes are propagated across all microservices, then consistency is improved, but propagation time and system overhead increase
Solution Approach 1:
The patent segments the microservice configuration system into domain-based groups and hierarchical levels. Configuration changes can be propagated selectively to specific domains or subsets of services rather than forcing a complete system-wide propagation. This segmentation allows for optimized propagation paths that reduce unnecessary transmission across the entire system.
Solution Approach 2:
The configuration propagation mechanism is designed to be dynamic, adjusting the propagation scope and timing based on the specific changes made. The system can propagate configurations immediately or schedule them, and can target specific domain groups rather than all services uniformly. This dynamic approach optimizes propagation time while maintaining necessary consistency.
3Productivity
If all microservice settings are stored centrally, then management efficiency is improved, but data access latency and single point of failure risk increase
Solution Approach 1:
The system pre-organizes configuration data into a hierarchical domain structure with defined relationships and dependencies. Configuration validation rules and propagation paths are established in advance, allowing the system to quickly retrieve and apply configurations without performing complex computations at access time. This preliminary structuring reduces access latency while maintaining centralized management.
Data Source
AI summary
Disclosed embodiments are directed at systems, methods, and architecture for operating a control plane of a microservice architecture application. The control plane may link a plurality of APIs for the microservice architecture application. The communication between the APIs and the control plane enables the control plane to assess the settings of the APIs compared to stored versions of the settings. The settings and stored versions may each be hashed with a hashing algorithm. The control plane may instruct APIS to update their settings responsive to determining that the settings do not match the stored versions.