Microservice Resource Limiting via Gateway Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems struggle to efficiently monitor and limit the overall resource usage of microservice-based applications in cloud environments, which can lead to resource overuse impacting other customers.
Innovation Solution
Implementing a system where request-specific resource usage limits are associated with different types of requests and tenants, and these limits are dynamically updated and enforced across multiple microservices, ensuring that resource usage does not exceed predefined thresholds.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If microservice-based applications are deployed in cloud environments to take advantage of resource elasticity and scalability, then the application's adaptability and productivity are improved, but the complexity of monitoring and limiting resource usage across multiple independent microservices increases
Solution Approach 1:
The patent segments the resource usage limit into multiple components, each associated with different microservices. The gateway service divides the total resource limit into portions that are distributed to individual microservices, allowing independent monitoring and control of resource usage across the distributed system while maintaining overall resource constraints.
2Ease of operation
If resource usage is monitored within a single server processing monolithic applications, then the monitoring mechanism is simple and straightforward, but this approach cannot be effectively applied to distributed microservice architectures where requests are processed across multiple independent services
Solution Approach 1:
The patent introduces a gateway service as an intermediary between external requests and the microservice cluster. The gateway receives requests, determines resource usage limits, and distributes these limits to the appropriate microservices. This intermediary approach enables centralized resource limit management while maintaining the distributed nature of the microservice architecture.
Solution Approach 2:
The patent implements preliminary action by determining and setting resource usage limits for microservices before requests are processed. The gateway service pre-calculates resource limits based on the request type and tenant, then distributes these limits to microservices in advance, enabling proactive resource management rather than reactive monitoring.
3Reliability
If resource usage limits are set for microservice-based applications, then resource overuse can be prevented, but the complexity of dynamically updating and enforcing these limits across multiple independent microservices increases
Solution Approach 1:
The patent implements feedback mechanisms where microservices report their resource usage back to the gateway service. The gateway monitors the accumulated resource usage across all microservices and can dynamically adjust limits or reject requests when thresholds are approached, creating a closed-loop control system that maintains resource usage within defined boundaries.
Data Source
AI summary
Systems and methods provide reception of a request including a resource usage limit associated with a computing resource, execution of processing in response to the request, determination of an amount of the computing resource consumed during the processing, update of the resource usage limit based on the determined amount, determination that the resource usage limit has not been reached based on the updated resource usage limit, and, in response to the determination that the updated resource usage limit has not been reached, return a response to the request including the updated resource usage limit.