Hot Upgrading Microservice Sequences Without Disruption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud computing environments cannot support the hot upgrading of a sequence of microservices without causing errors or requiring the sequence to be stopped, leading to service disruptions.
Innovation Solution
A method for hot upgrading a sequence of microservices in a cloud computing environment involves determining the status of each microservice or subsequence and invoking the next one only when it is upgrade-complete, using a processor to manage the sequence instance and handle unexecuted microservices or subsequences based on an ordered list, allowing for seamless upgrades without service interruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If hot upgrading is attempted in current cloud computing environments, then microservice updates can be applied, but service disruptions and errors occur requiring sequence停止
Solution Approach 1:
The patent implements preliminary action by checking the status of each microservice in the sequence before invoking it. The system determines whether a microservice is upgrade-complete before attempting to invoke it, ensuring that only upgraded microservices are called. This prevents service disruptions by preparing the upgrade state in advance and verifying it before execution.
Solution Approach 2:
The patent employs feedback mechanisms by continuously monitoring the status of microservices during the upgrade process. The system checks whether each microservice has completed its upgrade before proceeding to the next one, and invokes the next microservice only when the current one is upgrade-complete. This feedback loop ensures reliable service continuity during hot upgrading.
2Adaptability or versatility
If sequence is stopped for hot upgrading, then microservices can be upgraded, but service operations are disrupted
Solution Approach 1:
The patent ensures continuity of useful action by implementing a hot upgrade mechanism that does not require stopping the sequence. The system can determine microservice status and invoke upgraded microservices while the sequence is running, maintaining continuous service operations. This allows upgrades to occur without interrupting productivity.
3Speed
If next microservice is invoked immediately without status check, then response time is reduced, but upgrade errors occur
Solution Approach 1:
The patent uses feedback by checking the status of each microservice before invocation. The system determines whether a microservice is upgrade-complete and only invokes it when the status indicates readiness. This feedback mechanism ensures reliable upgrades while maintaining efficient response times through targeted status verification.
Solution Approach 2:
The patent implements preliminary action by pre-checking the upgrade status of microservices before invocation. The system determines in advance whether a microservice is ready to be invoked, and only then proceeds with the invocation. This preliminary status determination ensures reliability while minimizing delays.
Data Source
AI summary
Approaches presented herein enable hot upgrading a microservices sequence in a cloud computing environment. More specifically, a next microservice of microservice subsequence in a running sequence is obtained, in response to a message to invoke the microservice or subsequence. The running microservice sequence includes at least one unexecuted microservice or subsequence that is to be hot upgraded. The running microservice sequence is generated based on a sequence that is to be hot upgraded which comprises an ordered list of microservices and/or subsequences. The approach may include determining the status of a next microservice or subsequence. The approach may further include invoking the next microservice or subsequence in the running sequence, in response to the status of the next microservice or subsequence being upgrade-complete.