Microservice API Fault Manager for Container Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current container orchestration platforms fail to effectively validate and remediate unresponsive APIs in microservice environments, leading to undetected faults and application unresponsiveness, as they lack the capability to perform API validation and healing, and existing solutions are either ineffective or costly in terms of performance degradation.
Innovation Solution
A microservice API fault manager (MAFM) system that identifies unresponsive APIs, determines remedial actions using a machine-learning model, and communicates these actions to the container orchestration platform to terminate and replace faulty containers, ensuring API validation and healing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If container orchestration platforms are used to manage microservices, then service deployment and scaling efficiency is improved, but the ability to detect and remediate unresponsive APIs deteriorates
Solution Approach 1:
The patent introduces an API fault manager as an intermediary component that sits between the container orchestration platform and the microservices. This mediator actively monitors API endpoints, detects unresponsive services, and coordinates remediation actions, thereby filling the monitoring gap without replacing the orchestration platform's deployment functions.
Solution Approach 2:
The system implements continuous feedback loops where the API fault manager monitors API endpoints, detects failures, triggers remediation actions, and verifies recovery status. This closed-loop feedback mechanism ensures that unresponsive APIs are automatically detected and corrected, maintaining system reliability while preserving orchestration efficiency.
2Reliability
If existing API validation solutions are implemented, then API fault detection capability is improved, but performance degradation increases
Solution Approach 1:
The API fault manager implements selective monitoring by focusing only on critical API endpoints and high-priority microservices rather than monitoring all services uniformly. This partial action approach maintains adequate fault detection capability while minimizing the performance overhead associated with comprehensive monitoring of every service.
Solution Approach 2:
The system performs preliminary health checks and validation of API endpoints before they are fully integrated into service traffic. By pre-validating APIs and detecting potential failures early, the system avoids the performance penalty of detecting and remediating failures after they impact production traffic.
Data Source
AI summary
A method, system and computer program product for improving the availability of API endpoints in container orchestration platforms. A service request handler module of a microservice application programming interface (API) fault manager (MAFM) invokes a microservice API fault management service in response to detecting an unresponsive microservice managed by a container orchestration platform. An API inspection module of the MAFM identifies an unresponsive API of the unresponsive microservice. A remedial action module of the MAFM determines a remedial action to correct an unresponsive state of the unresponsive API. A container platform interface module of the MAFM communicates the remedial action to the container orchestration platform.