17945003. MICROSERVICE TERMINATION WHILE MAINTAINING HIGH AVAILABILITY simplified abstract (MICROSOFT TECHNOLOGY LICENSING, LLC)
Contents
- 1 MICROSERVICE TERMINATION WHILE MAINTAINING HIGH AVAILABILITY
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 MICROSERVICE TERMINATION WHILE MAINTAINING HIGH AVAILABILITY - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
MICROSERVICE TERMINATION WHILE MAINTAINING HIGH AVAILABILITY
Organization Name
MICROSOFT TECHNOLOGY LICENSING, LLC
Inventor(s)
Karthik Maharajan Sankara Subramanian of Bellevue WA (US)
MICROSERVICE TERMINATION WHILE MAINTAINING HIGH AVAILABILITY - A simplified explanation of the abstract
This abstract first appeared for US patent application 17945003 titled 'MICROSERVICE TERMINATION WHILE MAINTAINING HIGH AVAILABILITY
Simplified Explanation
The techniques disclosed in this patent application aim to reduce the time required to terminate a set of microservices for an application while ensuring high availability and preventing request failures. This is achieved through a termination manager that analyzes outstanding requests and constructs call graphs to determine which microservices are needed to process the requests.
- The termination manager retrieves request queues for the microservices to analyze outstanding requests.
- Based on the outstanding requests, the termination manager constructs call graphs for each request to determine the necessary microservices.
- Microservices that do not appear in the call graphs are identified as unneeded and can be terminated.
- The termination manager gradually terminates the remaining microservices as requests are processed.
Potential Applications
The technology described in this patent application could be applied in various industries where microservices are used to process requests, such as cloud computing, e-commerce platforms, and online services.
Problems Solved
This technology addresses the challenge of efficiently terminating a set of microservices while ensuring that all outstanding requests are processed without failures. It helps maintain high availability and optimize resource usage in a microservices architecture.
Benefits
- Reduced time required to terminate microservices - Prevention of request failures - Improved resource management and high availability in microservices architecture
Potential Commercial Applications
The technology could be valuable for companies operating large-scale applications with microservices architecture, such as cloud service providers, online retailers, and social media platforms.
Possible Prior Art
One possible prior art could be techniques for managing microservices termination in cloud computing environments, but the specific approach of analyzing outstanding requests and constructing call graphs to determine necessary microservices may be novel.
Unanswered Questions
How does this technology impact the scalability of microservices architecture?
This article does not delve into the scalability aspect of the technology. It would be interesting to explore how the approach described here could be scaled for applications with a large number of microservices and requests.
What are the potential security implications of using a termination manager for microservices?
The security aspect of the technology is not discussed in detail in this article. It would be important to consider how the termination manager could impact the security of the microservices and the overall application architecture.
Original Abstract Submitted
The techniques disclosed herein enable systems to reduce the time required to terminate a set of microservices for an application while ensuring high availability and preventing request failures. This is accomplished through a termination manager which retrieves request queues for the microservices to analyze outstanding requests that require processing prior to termination. Based on the outstanding requests, the termination manager constructs call graphs for each request. The call graphs capture the operational flow of the associated request by defining a sequence of microservices whose functionality is invoked by the request. From an initial analysis, the termination manager can determine that some of the microservices do not appear in the call graphs, indicating that the microservices are not needed to process the outstanding requests. Accordingly, the unneeded microservices are terminated. As requests are processed by the remaining microservices, the termination manager gradually terminates the remaining microservices based on the call graphs.
