Microservice Update Evaluation via Pre-Post Flow Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Web services constructed by mashup of microservices, existing methods fail to effectively evaluate the impact of upgraded microservices on the entire service, particularly when multiple functions are involved, and do not consider scenarios where a module is related to multiple functions or services.
Innovation Solution
A program operation system that includes a microservice management unit to execute pre-update and post-update service flows, and a service update analysis processing unit to evaluate these flows using KPI values, selecting the flow with higher performance and registering it as a new service flow for deployment, allowing continuous evaluation of updated microservices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If microservices are upgraded by adding new functions or corrections, then service functionality is improved, but the impact and defects on the entire Web service cannot be properly evaluated
Solution Approach 1:
The patent applies preliminary action by executing a pre-update service flow that includes the microservice before update, and comparing it with the post-update service flow. This allows the system to evaluate the impact of upgrades before they are fully deployed, ensuring that defects are detected and service reliability is maintained while still improving functionality.
2Productivity
If individual microservices are upgraded, then new functions are added, but it is not considered to evaluate the influence of the changed module on the entire service
Solution Approach 1:
The patent implements feedback by evaluating the execution results of both pre-update and post-update service flows, and using this evaluation information to determine whether to apply the upgrade. The system feeds back the impact assessment of changed modules on the entire service, ensuring that productivity improvements do not result in loss of service impact information.
3Device complexity
If a module is related to a plurality of functions, then service complexity is reduced, but existing methods cannot handle this scenario
Solution Approach 1:
The patent applies universality by creating a comprehensive evaluation method that handles modules related to multiple functions. The service flow evaluation mechanism is designed to work regardless of how many functions a module is related to, making the upgrade evaluation process universally applicable to complex service architectures where modules serve multiple purposes.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
There is provided a microservice management unit that, in a service provided by executing one or a plurality of microservices, executes a pre-update service flow including a microservice before update and a post-update service flow including a microservice after update, and outputs an execution result of the pre-update service flow and an execution result of the post-update service flow, and a service update analysis processing unit that evaluates the execution result of the pre-update service flow and the execution result of the post-update service flow, and as a service flow in which the evaluation result satisfies a predetermined relation, selects either the pre-update service flow or the post-update service flow.