Microservice Coordinator for Dynamic Maintenance and Overload Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed computing environments, primary services often experience performance degradation due to overwhelming requests on secondary or tertiary services, leading to inefficiencies and resource depletions when multiple instances lack coordination.
Innovation Solution
A centralized coordinator dynamically manages multiple microservice instances by monitoring performance metrics and resource consumption, adjusting processing capacity, and coordinating execution requests to prevent overload and maintain operational limits, using a service topography and predefined rules to create and execute maintenance plans.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple primary services simultaneously access secondary or tertiary services, then the primary services can perform their specialized operations, but the secondary or tertiary service becomes overwhelmed with requests leading to degraded performance
Solution Approach 1:
The patent introduces a coordinator service as an intermediary between primary services and secondary/tertiary services. This coordinator monitors the topography (current state and capacity) of secondary services and regulates access from primary services accordingly, preventing overload while maintaining system productivity
Solution Approach 2:
The system implements continuous feedback loops where the coordinator monitors service status, evaluates it against predefined rules, and dynamically adjusts access permissions. This feedback mechanism ensures that primary services are allowed to access secondary services only when capacity is available, maintaining both productivity and reliability
2Reliability
If a centralized coordinator dynamically manages multiple microservice instances by monitoring performance metrics and coordinating execution requests, then service overload is prevented and operational limits are maintained, but system complexity increases
Solution Approach 1:
The coordinator dynamically changes system parameters (access permissions, execution timing, resource allocation) based on monitored service status. By adjusting these parameters in real-time according to predefined rules, the system maintains reliability without requiring complex hard-coded control logic
Solution Approach 2:
The system transitions from static service management to dynamic coordination where access permissions and execution plans are continuously adapted based on current topography. This dynamic approach allows the system to respond to changing conditions while maintaining manageable complexity through rule-based decision-making
3Ease of manufacture
If maintenance operations are executed on service instances, then service updates and maintenance are performed, but service availability and performance may be degraded during maintenance
Solution Approach 1:
The coordinator creates execution plans that schedule maintenance operations in advance, evaluating current topography and selecting optimal timing. By performing preliminary assessment and scheduling, maintenance can be executed with minimal impact on service availability
Solution Approach 2:
Maintenance operations are executed periodically based on predefined schedules and current service status. The coordinator monitors service health and triggers maintenance at appropriate intervals, ensuring that updates are performed systematically without causing continuous service degradation
Data Source
AI summary
Techniques are provided for a coordinated microservice system including a coordinator and multiple services, which interact with each other. Each of the services can have multiple execution instances, which run independently of each other. In operation, the current status of each instance is evaluated against one or more rules to determine whether the current status changes the topography of the services and updating the topography based on the changes. An execution plan is created for executing a command based on one or more predefined rules and the updated topography, where the execution plan includes one or more steps for executing the command on each instance of the service. The execution plan is executed on each instance of the service in accordance with the one or more predefined rules.