System evaluation methods, apparatus, computer-readable storage media and electronic devices

Abstract

This invention discloses a system evaluation method, apparatus, computer-readable storage medium, and electronic device. Relating to the fields of fintech or other fields, the method includes: identifying multiple service units to be evaluated from the service integration layer of a target system; obtaining the microservice call information of each service unit to be evaluated when responding to business requests within a preset time, as well as the operation information of the called microservices; and evaluating the combined value between two target service units to be evaluated based on the call information and operation information corresponding to two target service units to be evaluated. This invention solves the technical problem of low evaluation accuracy caused by the reliance on manual evaluation of the necessity for merging service units in the service integration layer in related technologies.

Description

Technical Field

[0001] This invention relates to the field of financial technology or other fields, and more specifically, to a system evaluation method, apparatus, computer-readable storage medium, and electronic device. Background Technology

[0002] Software layering is a common architectural design pattern that divides software components into several parallel layers, suitable for systems integrating different functions. Based on currently used layered architectural design principles, such as... Figure 1 As shown, a large-scale information system can contain multiple channel entry points (UI, User Interface) and user interaction layers (BFF, Backend for Frontend), with one UI corresponding to one user interaction layer. The user interaction layer completes the corresponding business functions by requesting the service integration layer. The service integration layer is usually built as a business middle platform, and can be subdivided into different domain middle platforms according to business domains. In a microservice architecture, each domain middle platform provides several service units that complete different business processing capabilities, and the service units encapsulate the atomic services of multiple corresponding business systems.

[0003] Because different user interaction layers, domain middleware, and business systems are developed independently by different teams, the teams cannot accurately understand the internal implementation logic of the upstream and downstream. As a result, when designing and implementing service units, the middleware usually has many service units with similar functions, which leads to high maintenance costs for the related systems where the middleware is located. To solve this problem, it is usually necessary to rely on manual experience to assess the necessity of merging the design of each service unit in the service integration layer, which results in low assessment accuracy and makes it impossible to effectively merge related service units.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This invention provides a system evaluation method, apparatus, computer-readable storage medium, and electronic device to at least address the technical problem of low evaluation accuracy caused by the reliance on manual evaluation of the necessity of merging the design of each service unit in the service integration layer in related technologies.

[0006] According to one aspect of the present invention, a system evaluation method is provided, comprising: determining a plurality of service units to be evaluated from a service integration layer of a target system, wherein the service integration layer includes a plurality of service units, each service unit to be evaluated encapsulates at least one microservice of a business system, each service unit to be evaluated responds to a business request by calling the microservice, and the business request is sent to the service integration layer through a user interaction layer in the target system; obtaining call information of the microservices by each service unit to be evaluated when responding to the business request within a preset time, and operation information of the called microservices, wherein the operation information characterizes the operation record corresponding to the called microservices when executing target operation content, and the target operation content is used to process the business request; evaluating the merging value between two target service units to be evaluated based on the call information and operation information corresponding to two target service units to be evaluated, wherein the two target service units to be evaluated are any two different service units among the plurality of service units to be evaluated, the merging value characterizes the importance of merging the two service units to be evaluated, and the merging value is used to determine whether to merge the two service units to be evaluated.

[0007] Furthermore, the system evaluation method also includes: based on the call information and operation information corresponding to the two target service units to be evaluated, determining the microservices called by each target service unit to be evaluated when responding to business requests within a preset time, and the target operation content of the called microservices, to obtain a first data result; based on the call information and operation information corresponding to the two target service units to be evaluated, determining the number of times the called microservices corresponding to each target service unit to be evaluated are called within a preset time, and the number of operations corresponding to the target operation content of the called microservices, to obtain a second data result; and based on at least one of the first data result and the second data result, evaluating the combined value between the two target service units to be evaluated.

[0008] Furthermore, the system evaluation method also includes: calculating the operational similarity between two target service units to be evaluated based on the first data result, wherein the operational similarity is used to characterize the similarity of the operational content corresponding to the two target service units to be evaluated; calculating the transaction similarity between the two target service units to be evaluated based on the second data result, wherein the transaction similarity is used to characterize the similarity of the processing process of the two target service units to be evaluated for transaction requests; and evaluating the combined value between the two target service units to be evaluated based on at least one of the operational similarity and the transaction similarity.

[0009] Furthermore, the system evaluation method also includes: determining the data result corresponding to the first target service unit from the first data result to obtain the first target data result, and constructing a first matrix based on the first target data result, wherein the first target service unit is any one of the two target service units to be evaluated; determining the data result corresponding to the second target service unit from the first data result to obtain the second target data result, and constructing a second matrix based on the first target data result, wherein the second target service unit is any one of the two target service units to be evaluated other than the first target service unit; calculating the cosine similarity between the first matrix and the second matrix to obtain a first calculation result; and determining the operational similarity between the first target service unit and the second target service unit based on the first calculation result.

[0010] Furthermore, the system evaluation method also includes: determining the data result corresponding to the first target service unit from the second data result to obtain the third target data result, and constructing a third matrix based on the third target data result; determining the data result corresponding to the second target service unit from the second data result to obtain the fourth target data result, and constructing a fourth matrix based on the fourth target data result; calculating the cosine similarity between the third matrix and the fourth matrix to obtain the second calculation result; and determining the transaction similarity between the first target service unit and the second target service unit based on the second calculation result.

[0011] Furthermore, the system evaluation method also includes: after evaluating the merging value between the two target service units to be evaluated based on the call information and operation information corresponding to the two target service units to be evaluated, determining multiple third target service units from multiple service units to be evaluated based on the merging value between the two target service units to be evaluated, wherein the third target service units are service units to be merged and designed.

[0012] Furthermore, the system evaluation method also includes: after determining multiple third target service units from multiple service units to be evaluated, determining the number of business requests responded to by each third target service unit within a preset time; and determining service units to be deleted from multiple third target service units based on the number of requests corresponding to each third target service unit, wherein the service units to be deleted are service units that can be deleted during the merge design process.

[0013] According to another aspect of the present invention, a system evaluation apparatus is also provided, comprising: a first determining module, configured to determine a plurality of service units to be evaluated from a service integration layer of a target system, wherein the service integration layer includes a plurality of service units, each service unit to be evaluated encapsulates at least one microservice of a business system, each service unit to be evaluated responds to a business request by calling the microservice, and the business request is sent to the service integration layer through a user interaction layer in the target system; an obtaining module, configured to obtain the calling information of the microservice by each service unit to be evaluated when responding to the business request within a preset time, and the operation information of the called microservice, wherein the operation information characterizes the operation record corresponding to the called microservice when performing the target operation content, and the target operation content is used to process the business request; and an evaluation module, configured to evaluate the merging value between two target service units to be evaluated based on the calling information and the operation information corresponding to the two target service units to be evaluated, wherein the two target service units to be evaluated are any two different service units among the plurality of service units to be evaluated, the merging value characterizes the importance of merging the two service units to be evaluated, and the merging value is used to determine whether to merge the two service units to be evaluated.

[0014] According to another aspect of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer-readable storage medium, and the computer program is configured to execute the above-described system evaluation method at runtime.

[0015] According to another aspect of the present invention, an electronic device is also provided, the electronic device including one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are configured to run the programs, wherein the programs are configured to execute the above-described system evaluation method during runtime.

[0016] In this embodiment of the invention, a method is adopted to evaluate the merging value between service units based on the corresponding call information and operation information of service units in the service integration layer. This involves identifying multiple service units to be evaluated from the service integration layer of the target system, then obtaining the call information of each service unit to the microservices it responds to within a preset time, as well as the operation information of the called microservices. Based on the call information and operation information corresponding to two target service units to be evaluated, the merging value between them is evaluated. The service integration layer includes multiple service units, each of which encapsulates at least one microservice from a business system. Each service unit responds to a business request by calling a microservice. The business request is sent to the service integration layer through the user interaction layer of the target system. The operation information represents the operation record corresponding to the called microservice executing the target operation content, which is used to process the business request. The two target service units to be evaluated are any two different service units among the multiple service units to be evaluated. The merging value represents the importance of merging the two service units to be evaluated, and is used to determine whether to merge the two service units to be evaluated.

[0017] In the above process, based on the call information and operation information corresponding to the two target service units to be evaluated, the execution content when each service unit processes business requests can be determined. This effectively determines the degree of similarity between the two target service units to be evaluated in terms of execution content. Furthermore, based on the degree of similarity in the execution content of the two target service units to be evaluated, the merging value between the two service units to be evaluated can be determined. This enables the accurate determination of the service units to be merged in the service integration layer based on the merging value, improving the evaluation accuracy and avoiding the technical problem of low evaluation accuracy caused by the reliance on manual evaluation of the merging design of each service unit in the service integration layer in related technologies.

[0018] Therefore, the solution provided in this application achieves the goal of evaluating the combined value between service units based on the corresponding call information and operation information of the service units in the service integration layer, thereby improving the technical effect of evaluation accuracy. It also solves the technical problem of low evaluation accuracy caused by the reliance on manual evaluation of the necessity of merging the service units in the service integration layer in related technologies. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0020] Figure 1This is a schematic diagram of an optional evaluation system according to an embodiment of the present invention;

[0021] Figure 2 This is a schematic diagram of an optional system evaluation method according to an embodiment of the present invention;

[0022] Figure 3 This is a schematic diagram of an optional business processing system according to an embodiment of the present invention;

[0023] Figure 4 This is a schematic diagram of an optional service unit according to an embodiment of the present invention;

[0024] Figure 5 This is a schematic diagram illustrating the execution content of an optional service unit according to an embodiment of the present invention;

[0025] Figure 6 This is a schematic diagram illustrating the execution content of an optional service unit according to an embodiment of the present invention;

[0026] Figure 7 This is a schematic diagram of the service unit transaction volume of an optional service unit according to an embodiment of the present invention;

[0027] Figure 8 This is a schematic diagram of an optional system evaluation apparatus according to an embodiment of the present invention;

[0028] Figure 9 This is a schematic diagram of an optional electronic device according to an embodiment of the present invention. Detailed Implementation

[0029] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] It should be noted that the system evaluation methods, apparatus, computer-readable storage media and electronic devices proposed in this disclosure can be used in the field of fintech, or in any field other than fintech. The application fields of the system evaluation methods, apparatus, computer-readable storage media and electronic devices proposed in this disclosure are not limited.

[0032] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0033] Example 1

[0034] According to an embodiment of the present invention, an embodiment of a system evaluation method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0035] In this embodiment, as Figure 1 As shown, the aforementioned system evaluation method is executed using an optional evaluation system as the execution subject. The evaluation system includes a triggering unit, an analysis unit, and a storage unit.

[0036] Figure 2 This is a schematic diagram of an optional system evaluation method according to an embodiment of the present invention, such as... Figure 2 As shown, the method includes the following steps:

[0037] Step S201: Identify multiple service units to be evaluated from the service integration layer of the target system. The service integration layer includes multiple service units. Each service unit to be evaluated encapsulates at least one microservice of a business system. Each service unit to be evaluated responds to a business request by calling the microservice. The business request is sent to the service integration layer through the user interaction layer of the target system.

[0038] Optionally, this application can be evaluated using an evaluation system. Figure 1 The business processing system shown (i.e., the aforementioned target system) will be evaluated. First, the architecture and workflow of the business processing system will be described. The architecture diagram of the business processing system is shown below. Figure 3 As shown, it includes a UI layer, a user interaction layer, a service integration layer, and a business processing layer. Different UI layers correspond to different channels, such as mobile software channels, PC channels (i.e., web channels), telephone communication channels, and third-party channels. Each channel's UI has a corresponding user interaction layer. The service integration layer includes domain-specific platforms (such as...) corresponding to different business domains. Figure 1 As shown in Domain Platform 1 and Domain Platform 2, each domain platform provides several service units that perform different business processing capabilities, and each service unit encapsulates at least one microservice of a business system. Figure 3 The domain platform shown provides service units such as IS1, IS2, and IS3 for different user interaction layers to call. Specifically, the IS1 service unit encapsulates microservices such as CSA1, CSB1, and CSA2; the IS2 service unit encapsulates microservices such as CSB1 and CSC1; and the IS3 service unit encapsulates microservices such as CSA1 and CSC2. Furthermore, in Figure 1 In this context, microservices refer to products A, B, C, and D.

[0039] In the process of business processing in the system, users send business requests through the UI layer, which processes these requests and then forwards them to the corresponding service unit in the service integration layer. Upon receiving the request, the service unit invokes at least one of its encapsulated microservices to process the request. The service unit then retrieves the processing result from the microservice and returns it to the user interaction layer, thus completing the processing of the relevant business logic.

[0040] In step S201, the triggering unit in the evaluation system is used to determine the time for performing the system evaluation, for example, performing the evaluation regularly once a month. Optionally, such as... Figure 1As shown, the triggering unit can also determine the time for system evaluation based on the proactive triggering requests from various domain platforms. When the triggering unit notifies the analysis unit that a system evaluation is required, the analysis unit can identify service units belonging to the same domain platform in the target system as a group of service units to be evaluated.

[0041] Step S202: Obtain the microservice call information of each service unit to be evaluated when responding to business requests within a preset time, as well as the operation information of the called microservice. The operation information represents the operation record corresponding to the called microservice when executing the target operation content, and the target operation content is used to process the business request.

[0042] The evaluation system can provide multiple common components, which are then configured in each service unit and business system. These common components monitor the operation of microservices within each service unit and business system, enabling the acquisition of call and operation information for each service unit to be evaluated. Subsequently, as... Figure 1 As shown, the common component can send call information and operation information to the storage unit for storage. Each business request has a scenario code and an event number. The event number is a unique identifier corresponding to the business request. The evaluation system can record a series of operations performed by the service unit being evaluated when executing the business request, based on the event number. The scenario code is used to identify at least the access party corresponding to the business request. The evaluation system can determine the source of the business request and the number of access parties based on the scenario code. The common component can control the collection of information on / off and can preset the collection time period. Each channel can correspond to multiple access parties, and different access parties can correspond to different functional windows within the current channel.

[0043] Optionally, in step S202, when a system evaluation is required, such as... Figure 1 As shown, the analysis unit can obtain from the storage unit the microservice call information of each service unit to be evaluated when responding to business requests within a preset time, as well as the operation information of the called microservices. Specifically, the call information for each service unit to be evaluated may include the microservices called by that service unit when processing different business requests, and the time of the microservice call. The call information for each service unit to be evaluated may also include the operation content (i.e., the target operation content) performed by the microservices called by that service unit to process different business requests.

[0044] It should be noted that by obtaining the call information and operation information corresponding to each service unit to be evaluated, it is possible to determine the execution content when each service unit processes business requests.

[0045] Step S203: Based on the call information and operation information corresponding to the two target service units to be evaluated, evaluate the merging value between the two target service units to be evaluated. The two target service units to be evaluated are any two different service units among multiple service units to be evaluated. The merging value characterizes the importance of merging the two service units to be evaluated. The merging value is used to determine whether to merge the two service units to be evaluated.

[0046] In step S203, the analysis unit can arbitrarily select a service unit to be evaluated from multiple service units to be evaluated as a target service unit to be evaluated. Then, it determines the call information and operation information corresponding to the two target service units to be evaluated. After that, the analysis unit can determine the similarity of the operation content performed by the two target service units to be evaluated when calling the microservice, and / or the similarity of the transaction requests processed by the two target service units to be evaluated, based on the determined similarity.

[0047] It should be noted that, based on the call information and operation information corresponding to the two target service units to be evaluated, the degree of similarity between the two target service units to be evaluated in terms of execution content can be effectively determined. Thus, based on the degree of similarity in the execution content of the two target service units to be evaluated, the merging value between the two service units to be evaluated can be determined. In this way, the service units to be merged in the service integration layer can be accurately determined according to the merging value, which improves the evaluation accuracy and avoids the technical problem of low evaluation accuracy caused by the necessity of manual evaluation to merge the service units in the service integration layer in related technologies.

[0048] Based on the scheme defined in steps S201 to S203 above, it can be understood that in this embodiment of the invention, the method of evaluating the merging value between service units is adopted based on the call information and operation information corresponding to the service units in the service integration layer. By determining multiple service units to be evaluated from the service integration layer of the target system, and then obtaining the call information of each service unit to be evaluated to the microservice when responding to the business request within a preset time, as well as the operation information of the called microservice, the merging value between the two target service units to be evaluated is evaluated based on the call information and operation information corresponding to the two target service units to be evaluated. The service integration layer comprises multiple service units. Each service unit to be evaluated encapsulates at least one microservice from a business system. Each service unit to be evaluated responds to business requests by calling the microservice. The business requests are sent to the service integration layer through the user interaction layer of the target system. Operation information represents the operation record corresponding to the microservice being called when it executes the target operation content. The target operation content is used to process the business request. The two target service units to be evaluated are any two different service units among the multiple service units to be evaluated. The merging value represents the importance of merging the design of the two service units to be evaluated. The merging value is used to determine whether to merge the design of the two service units to be evaluated.

[0049] It is noteworthy that, in the above process, based on the call information and operation information corresponding to the two target service units to be evaluated, the execution content of each service unit when processing business requests can be determined. This effectively determines the degree of similarity between the two target service units to be evaluated in terms of execution content. Furthermore, based on the degree of similarity in the execution content of the two target service units to be evaluated, the merging value between the two service units to be evaluated can be determined. This enables the accurate determination of the service units to be merged in the service integration layer based on the merging value, improving the evaluation accuracy and avoiding the technical problem of low evaluation accuracy caused by the reliance on manual evaluation of the necessity of merging the service units in the service integration layer in related technologies.

[0050] Therefore, the solution provided in this application achieves the goal of evaluating the combined value between service units based on the corresponding call information and operation information of the service units in the service integration layer, thereby improving the technical effect of evaluation accuracy. It also solves the technical problem of low evaluation accuracy caused by the reliance on manual evaluation of the necessity of merging the service units in the service integration layer in related technologies.

[0051] In one alternative embodiment, the processing of call information and operation information by the evaluation system is described.

[0052] Optionally, during the process of evaluating the combined value between two target service units based on their corresponding call information and operation information, the analysis unit can determine the microservices invoked by each target service unit when responding to each business request within a preset time, and the target operation content executed by the invoked microservices when processing each business request, thereby obtaining the first data result. For example, the business logic corresponding to the microservices encapsulated by a certain service unit is as follows: Figure 4 As shown, this service unit encapsulates three microservices: CS1, CS2, and CS3. CS1's business logic involves reading data table a (i.e., ...). Figure 4 After reading (a) in the middle, table b was written (i.e. Figure 4 In the context of writing (b), the business logic corresponding to CS2 is to call microservice CS4 to write table c (i.e., ...). Figure 4 After writing (c) in the middle, update table d (i.e., ... Figure 4 The write (d) in CS3 and the corresponding business logic is to read data table e (i.e. Figure 4 (e) in the context of reading. When this service unit is processing business request A, its actual execution content and execution logic are as follows: Figure 5 As shown in the paths corresponding to numbers 1-11, CS1 and CS2 are called sequentially, but CS3 is not called. The corresponding call information could be that this service unit called microservices CS1 and CS2 when responding to business request A. The corresponding operation information could be that CS1 read data from table a and wrote data to table b, and CS2 called microservice CS4 to write data to table c and update data to table d. It is important to emphasize that the same service unit may call microservices and perform different operations when responding to different business requests. Figure 6 The paths corresponding to numbers 1-10 show the execution content and logic of this service unit when processing business request B. This service unit sequentially calls CS1, CS2, and CS3, and the content of CS1 and CS2 changes. At this point, the service unit's call information indicates that it called microservices CS1, CS2, and CS3 when responding to business request B. The corresponding operation information could be that CS1 reads data table a, CS2 writes to table d, and CS3 reads table e.

[0053] Furthermore, the analysis unit can also determine the number of times each target service unit calls each microservice when responding to each business request within a preset time, based on the call information and operation information corresponding to the two target service units to be evaluated, and the number of times the target operation content corresponding to each business request is executed by the called microservice when processing the business request, thereby obtaining the second data result.

[0054] Furthermore, the analysis unit can assess the combined value between the two target service units to be evaluated based on at least one of the first data results and the second data results.

[0055] It should be noted that by determining the first and second data results based on the call information and operation information, the relevant data in the call information and operation information can be effectively extracted, thereby facilitating a more accurate assessment of the merging value.

[0056] In one optional embodiment, during the process of evaluating the combined value between two target service units to be evaluated based on at least one of a first data result and a second data result, the evaluation system can calculate the operational similarity between the two target service units to be evaluated based on the first data result and calculate the transaction similarity between the two target service units to be evaluated based on the second data result, thereby evaluating the combined value between the two target service units to be evaluated based on at least one of the operational similarity and transaction similarity. The operational similarity characterizes the similarity of the operational content corresponding to the two target service units to be evaluated, and the transaction similarity characterizes the similarity of the processing procedures of the two target service units to be evaluated for transaction requests.

[0057] Optionally, in the process of calculating the operational similarity between two target service units to be evaluated based on the first data results, the analysis unit can determine the data results corresponding to each target service unit to be evaluated from the first data results, then directly compare the two data results, and calculate the score based on the same parts and the score based on the different parts to obtain a score result, which can then be determined as the operational similarity between the target service units to be evaluated. Optionally, the analysis unit can also construct a corresponding matrix based on the data results corresponding to each target service unit to be evaluated, and then calculate the cosine similarity based on the matrix, thereby determining the cosine similarity as the operational similarity between the two target service units to be evaluated.

[0058] Optionally, in the process of calculating the transaction similarity between two target service units to be evaluated based on the second data results, the analysis unit can determine the data results corresponding to each target service unit to be evaluated from the second data results, then directly compare the two data results, and calculate the score based on the same parts and the score based on the different parts, thereby obtaining a score result, which can then be determined as the transaction similarity between the two target service units to be evaluated. Optionally, the analysis unit can also construct a corresponding matrix based on the data results corresponding to each target service unit to be evaluated, and then calculate the cosine similarity based on the matrix, thereby determining the cosine similarity as the transaction similarity between the two target service units to be evaluated.

[0059] Furthermore, the analysis unit can evaluate the combined value between two target service units based on at least one of operational similarity and transaction similarity. Optionally, when the analysis unit can evaluate the combined value between two target service units based on one of operational similarity and transaction similarity, the analysis unit can determine that a higher operational similarity indicates a higher combined value, or a higher transaction similarity indicates a higher combined value. When the analysis unit can evaluate the combined value between two target service units based on both operational similarity and transaction similarity, the analysis unit can assign different weights to operational similarity and transaction similarity, and determine the final similarity by weighted summation, thereby determining that a higher final similarity indicates a higher combined value between the two target service units.

[0060] It should be noted that by assessing the merger value based on the operational or transaction similarity between the two service units, a more accurate determination of the merger value is achieved.

[0061] In one optional embodiment, during the process of calculating the operational similarity between two target service units to be evaluated based on the first data result, the evaluation system can determine the data result corresponding to the first target service unit from the first data result to obtain the first target data result, construct a first matrix based on the first target data result, then determine the data result corresponding to the second target service unit from the first data result to obtain the second target data result, construct a second matrix based on the first target data result, calculate the cosine similarity between the first matrix and the second matrix to obtain a first calculation result, and thus determine the operational similarity between the first target service unit and the second target service unit based on the first calculation result. Here, the first target service unit is any one of the two target service units to be evaluated, and the second target service unit is any one of the two target service units to be evaluated other than the first target service unit.

[0062] Optionally, the analysis unit can construct a corresponding multi-dimensional matrix based on the execution hierarchy of the service unit recorded in the storage unit: "service unit - microservice - table operation (i.e., operation content)". For example, for Figure 4 The service unit shown, in the multi-dimensional matrix, has its first dimension containing CS1, CS2, and CS3; its second dimension containing read table a, write table b, CS4, write table d, and read table e; and its third dimension containing write table c. It should be noted that, to control the complexity of similarity calculation and the overhead of information storage, the number of levels in the tree structure of the storage unit recording the service unit can be freely set. For example, Figure 4 The tree structure shown has a depth of 3. If the write table c is omitted, the tree structure depth becomes 2. In addition, for the last level table operation, only the table name can be recorded, or it can be distinguished whether the table is read or written.

[0063] When determining the first or second matrix, if a microservice has been called, the value of the matrix element corresponding to that microservice is 1; if a microservice has not been called, the value of the matrix element corresponding to that microservice is 0. If an operation has been executed, the value of the matrix element corresponding to that operation is 1; if an operation has not been executed, the value of the matrix element corresponding to that operation is 0. This allows for the construction of the first and second matrices.

[0064] Then, the analysis unit can use the cosine similarity algorithm to calculate the cosine similarity between the first matrix and the second matrix, and obtain the first calculation result, as shown in the following formula:

[0065]

[0066] Where similarity(IS1,IS2) represents the first calculation result, IS1 represents the first target service unit, and IS2 represents the second target service unit.

[0067] Furthermore, the analysis unit can directly characterize the operational similarity between the first target service unit and the second target service unit through the first calculation result.

[0068] It should be noted that by calculating the cosine similarity between the first matrix and the second matrix, a more accurate calculation of the operational similarity between the first target service unit and the second target service unit is achieved, thereby further improving the evaluation accuracy.

[0069] In an optional embodiment, during the process of calculating the transaction similarity between two target service units to be evaluated based on the second data results, the evaluation system can determine the data results corresponding to the first target service unit from the second data results to obtain the third target data results, construct a third matrix based on the third target data results, then determine the data results corresponding to the second target service unit from the second data results to obtain the fourth target data results, construct a fourth matrix based on the fourth target data results, thereby calculating the cosine similarity between the third matrix and the fourth matrix to obtain the second calculation result, and then determining the transaction similarity between the first target service unit and the second target service unit based on the second calculation result.

[0070] Optionally, the methods for determining the dimensions of the third and fourth matrices are the same as those for the first and second matrices, and therefore will not be repeated here. It is important to emphasize that when determining the third or fourth matrix, one can first determine the ratio between the number of times each microservice corresponding to a service unit is invoked and the number of business requests entering that service unit. This ratio is then used as the value of the matrix element corresponding to a specific microservice. Subsequently, the analysis unit can also determine the ratio between the number of operations performed on the operation content of each microservice corresponding to a service unit and the number of business requests entering that service unit. This ratio is then used as the value of the matrix element corresponding to a specific operation content, thus enabling the construction of the third and fourth matrices.

[0071] The analysis unit then calculates the cosine similarity between the third and fourth matrices, obtaining a second calculation result. This second result directly characterizes the transaction similarity between the first and second target service units. Specifically, when the dimensions of the two matrices differ, they are adjusted to be identical by filling the blanks with zeros.

[0072] It should be noted that by calculating the cosine similarity between the third and fourth matrices, a more accurate calculation of the transaction similarity between the third and fourth target service units is achieved, thereby further improving the accuracy of the evaluation.

[0073] In an optional embodiment, after evaluating the combined value between two target service units based on the call information and operation information corresponding to the two target service units to be evaluated, the evaluation system can determine multiple third target service units from multiple service units to be evaluated based on the combined value between the two target service units to be evaluated, wherein the third target service units are service units to be designed for merging.

[0074] Optionally, the analysis unit may determine that the two target service units to be evaluated are the same group of service units to be merged (i.e., the third target service unit) when the combined value between the two target service units to be evaluated is greater than or equal to a preset value; otherwise, it may determine that the two target service units to be evaluated are service units not to be merged when the combined value between the two target service units to be evaluated is less than the preset value.

[0075] Afterwards, the analysis unit can display the list of third target service units and the calculated similarity results to relevant staff for merging design.

[0076] It should be noted that by determining the service units to be merged from multiple service units to be evaluated based on the merger value, the accurate determination of the service units to be merged is achieved.

[0077] In one optional embodiment, after determining multiple third target service units from multiple service units to be evaluated, the evaluation system determines the number of business requests responded to by each third target service unit within a preset time. Then, based on the number of requests corresponding to each third target service unit, it determines service units to be deleted from the multiple third target service units, wherein the service units to be deleted are service units that can be deleted during the merge design process.

[0078] Optional, such as Figure 7 As shown, Figure 7 The diagram shows the access party corresponding to each service unit and the transaction volume (i.e., the number of requests for the aforementioned business requests) sent by each access party to that service unit. Figure 7 The length of the rectangle corresponding to each access party represents the transaction volume sent by the service unit corresponding to each access party. The analysis unit can determine the service unit with the highest transaction volume in the same group of service units to be merged, based on the transaction volume received by each service unit, as the service unit that does not need to be deleted, and determine the other service units in the same group of service units to be merged as service units that can be deleted (i.e., the aforementioned service units to be deleted), and can feed back the determination results to relevant personnel. Optionally, the analysis unit can also determine the units to be deleted based on the above, combined with the number of access parties corresponding to each service unit. It should be noted that determining the service units to be deleted helps improve the optimization effect of the merged design.

[0079] It should be noted that in this application, by directly tracking the processing of business requests, recording the source of the requests and the microservices called, and calculating the merging value between service units, the merging value can be used as a reference and basis for merging design, which can effectively improve the service reuse value and reduce system maintenance costs.

[0080] Therefore, the solution provided in this application achieves the goal of evaluating the combined value between service units based on the corresponding call information and operation information of the service units in the service integration layer, thereby improving the technical effect of evaluation accuracy. It also solves the technical problem of low evaluation accuracy caused by the reliance on manual evaluation of the necessity of merging the service units in the service integration layer in related technologies.

[0081] Example 2

[0082] According to an embodiment of the present invention, a system evaluation apparatus is provided, wherein, Figure 8 This is a schematic diagram of a system evaluation apparatus for an optional service unit according to an embodiment of the present invention, such as... Figure 8 As shown, the device includes:

[0083] The first determining module 801 is used to determine multiple service units to be evaluated from the service integration layer of the target system. The service integration layer includes multiple service units, each service unit to be evaluated encapsulates at least one microservice of a business system, and each service unit to be evaluated responds to a business request by calling the microservice. The business request is sent to the service integration layer through the user interaction layer of the target system.

[0084] The acquisition module 802 is used to acquire the microservice call information of each service unit to be evaluated when responding to business requests within a preset time, as well as the operation information of the called microservice. The operation information represents the operation record corresponding to the called microservice when executing the target operation content, and the target operation content is used to process the business request.

[0085] The evaluation module 803 is used to evaluate the merging value between two target service units to be evaluated based on the call information and operation information corresponding to the two target service units to be evaluated. The two target service units to be evaluated are any two different service units among a plurality of service units to be evaluated. The merging value characterizes the importance of merging the two service units to be evaluated. The merging value is used to determine whether to merge the two service units to be evaluated.

[0086] It should be noted that the first determining module 801, the acquisition module 802 and the evaluation module 803 mentioned above correspond to steps S201 to S203 in the above embodiments. The examples and application scenarios implemented by the three modules and the corresponding steps are the same, but are not limited to the content disclosed in the above embodiment 1.

[0087] Optionally, the evaluation module further includes: a first determining submodule, used to determine, based on the call information and operation information corresponding to the two target service units to be evaluated, the microservices called by each target service unit to be evaluated when responding to business requests within a preset time, and the target operation content of the called microservices, to obtain a first data result; a second determining submodule, used to determine, based on the call information and operation information corresponding to the two target service units to be evaluated, the number of times the called microservices corresponding to each target service unit to be evaluated are called within a preset time, and the number of operations corresponding to the target operation content of the called microservices, to obtain a second data result; and a first evaluation submodule, used to evaluate the combined value between the two target service units to be evaluated based on at least one of the first data result and the second data result.

[0088] Optionally, the first evaluation submodule further includes: a first determining unit, configured to calculate the operational similarity between two target service units to be evaluated based on the first data result, wherein the operational similarity is used to characterize the similarity of the operational content corresponding to the two target service units to be evaluated; a second determining unit, configured to calculate the transaction similarity between the two target service units to be evaluated based on the second data result, wherein the transaction similarity is used to characterize the similarity of the processing process of the two target service units to be evaluated for transaction requests; and a first evaluation unit, configured to evaluate the combined value between the two target service units to be evaluated based on at least one of the operational similarity and the transaction similarity.

[0089] Optionally, the first determining unit includes: a first determining subunit, configured to determine the data result corresponding to the first target service unit from the first data result, obtain the first target data result, and construct a first matrix based on the first target data result, wherein the first target service unit is any one of the two target service units to be evaluated; a second determining subunit, configured to determine the data result corresponding to the second target service unit from the first data result, obtain the second target data result, and construct a second matrix based on the first target data result, wherein the second target service unit is any one of the two target service units to be evaluated other than the first target service unit; a first calculation subunit, configured to calculate the cosine similarity between the first matrix and the second matrix, and obtain a first calculation result; and a third determining subunit, configured to determine the operational similarity between the first target service unit and the second target service unit based on the first calculation result.

[0090] Optionally, the second determining unit includes: a fourth determining subunit, used to determine the data result corresponding to the first target service unit from the second data result, obtain the third target data result, and construct a third matrix based on the third target data result; a fifth determining subunit, used to determine the data result corresponding to the second target service unit from the second data result, obtain the fourth target data result, and construct a fourth matrix based on the fourth target data result; a second calculation subunit, used to calculate the cosine similarity between the third matrix and the fourth matrix, and obtain a second calculation result; and a sixth determining subunit, used to determine the transaction similarity between the first target service unit and the second target service unit based on the second calculation result.

[0091] Optionally, the system evaluation apparatus further includes: a second determining module, used to determine a plurality of third target service units from a plurality of service units to be evaluated based on the combined value between two target service units to be evaluated, wherein the third target service units are service units to be merged.

[0092] Optionally, the system evaluation device further includes: a third determining module, used to determine the number of business requests responded to by each third target service unit within a preset time; and a fourth determining module, used to determine the service unit to be deleted from multiple third target service units based on the number of requests corresponding to each third target service unit, wherein the service unit to be deleted is a service unit that can be deleted during the merge design process.

[0093] Example 3

[0094] According to another aspect of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the above-described system evaluation method at runtime.

[0095] Example 4

[0096] According to another aspect of the present invention, an electronic device is also provided, wherein, Figure 9 This is a schematic diagram of an optional electronic device according to an embodiment of the present invention, such as... Figure 9 As shown, the electronic device includes one or more processors; and a memory for storing one or more programs, which, when executed by one or more processors, enable the one or more processors to run the programs, wherein the programs are configured to execute the aforementioned system evaluation method during runtime.

[0097] Example 5

[0098] According to another aspect of the present invention, a computer program product is also provided, including a computer program / instructions that, when executed by a processor, implement the above-described features.

[0099] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0100] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0101] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0102] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0103] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0104] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0105] The above are merely preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A system evaluation method, characterized in that, include: Multiple service units to be evaluated are identified from the service integration layer of the target system. The service integration layer includes multiple service units. Each service unit to be evaluated encapsulates at least one microservice of a business system. Each service unit to be evaluated responds to a business request by calling the microservice. The business request is sent to the service integration layer through the user interaction layer of the target system. After receiving the business request, the service unit calls the microservice encapsulated in the service unit to process the business request and returns the processing result to the user interaction layer to complete the business process. Obtain the call information of each service unit to be evaluated to the microservice when responding to the business request within a preset time, as well as the operation information of the called microservice. The operation information represents the operation record corresponding to the called microservice when executing the target operation content, and the target operation content is used to process the business request. Based on the call information and operation information corresponding to the two target service units to be evaluated, the merging value between the two target service units to be evaluated is evaluated. The two target service units to be evaluated are any two different service units among the plurality of service units to be evaluated. The merging value characterizes the importance of merging the two service units to be evaluated. The merging value is used to determine whether to merge the two service units to be evaluated. Based on the call information and operation information corresponding to the two target service units to be evaluated, the combined value between the two target service units to be evaluated is evaluated, including: determining the microservices called by each target service unit to respond to the business request within a preset time, and the target operation content of the called microservices, based on the call information and operation information corresponding to the two target service units to be evaluated, to obtain a first data result; determining the number of times the called microservices corresponding to each target service unit to be evaluated are called within a preset time, and the number of operations corresponding to the target operation content of the called microservices, based on the call information and operation information corresponding to the two target service units to be evaluated, to obtain a second data result; and evaluating the combined value between the two target service units to be evaluated based on at least one of the first data result and the second data result, including: Based on the first data result, the operational similarity between the two target service units to be evaluated is calculated, wherein the operational similarity is used to characterize the similarity of the operational content corresponding to the two target service units to be evaluated; based on the second data result, the transaction similarity between the two target service units to be evaluated is calculated, wherein the transaction similarity is used to characterize the similarity of the processing process of the two target service units to be evaluated on the transaction request; based on at least one of the operational similarity and the transaction similarity, the combined value between the two target service units to be evaluated is evaluated.

2. The method according to claim 1, characterized in that, Based on the first data results, the operational similarity between the two target service units to be evaluated is calculated, including: The data result corresponding to the first target service unit is determined from the first data result to obtain the first target data result, and a first matrix is ​​constructed based on the first target data result, wherein the first target service unit is any one of the two target service units to be evaluated; The data result corresponding to the second target service unit is determined from the first data result to obtain the second target data result, and a second matrix is ​​constructed based on the first target data result, wherein the second target service unit is any one of the two target service units to be evaluated, excluding the first target service unit; Calculate the cosine similarity between the first matrix and the second matrix to obtain the first calculation result; Based on the first calculation result, the operational similarity between the first target service unit and the second target service unit is determined.

3. The method according to claim 1, characterized in that, Based on the second data results, the transaction similarity between the two target service units to be evaluated is calculated, including: The data result corresponding to the first target service unit is determined from the second data result, the third target data result is obtained, and a third matrix is ​​constructed based on the third target data result; The data result corresponding to the second target service unit is determined from the second data result to obtain the fourth target data result, and a fourth matrix is ​​constructed based on the fourth target data result; Calculate the cosine similarity between the third matrix and the fourth matrix to obtain the second calculation result; The transaction similarity between the first target service unit and the second target service unit is determined based on the second calculation result.

4. The method according to claim 1, characterized in that, After evaluating the combined value between the two target service units to be evaluated based on the call information and operation information corresponding to the two target service units to be evaluated, the method further includes: Based on the combined value between the two target service units to be evaluated, a plurality of third target service units are determined from the plurality of service units to be evaluated, wherein the third target service units are service units to be merged and designed.

5. The method according to claim 4, characterized in that, After determining a plurality of third target service units from the plurality of service units to be evaluated, the method further includes: Determine the number of business requests that each third target service unit responds to within a preset time. Based on the number of requests corresponding to each third target service unit, service units to be deleted are determined from multiple third target service units, wherein the service units to be deleted are those that can be deleted during the merge design process.

6. A system evaluation device, characterized in that, include: The first determining module is used to determine multiple service units to be evaluated from the service integration layer of the target system. The service integration layer includes multiple service units, each service unit to be evaluated encapsulates at least one microservice of a business system, and each service unit to be evaluated responds to a business request by calling the microservice. The business request is sent to the service integration layer through the user interaction layer of the target system. After receiving the business request, the service unit calls the microservice encapsulated in the service unit to process the business request and returns the processing result to the user interaction layer to complete the business process. The acquisition module is used to acquire the call information of each service unit to be evaluated to the microservice when responding to the business request within a preset time, as well as the operation information of the called microservice. The operation information represents the operation record corresponding to the called microservice when it executes the target operation content, and the target operation content is used to process the business request. The evaluation module is used to evaluate the merging value between two target service units to be evaluated based on the call information and operation information corresponding to the two target service units to be evaluated. The two target service units to be evaluated are any two different service units among the plurality of service units to be evaluated. The merging value represents the importance of merging the two service units to be evaluated. The merging value is used to determine whether to merge the two service units to be evaluated. The evaluation module further includes: a first determining submodule, used to determine, based on the call information and operation information corresponding to the two target service units to be evaluated, the microservices called by each target service unit to be evaluated when responding to the business request within a preset time, and the target operation content of the called microservices, to obtain a first data result; a second determining submodule, used to determine, based on the call information and operation information corresponding to the two target service units to be evaluated, the number of times the called microservices corresponding to each target service unit to be evaluated are called within a preset time, and the number of operations corresponding to the target operation content of the called microservices, to obtain a second data result; and a first evaluation submodule, used to evaluate the combined value between the two target service units to be evaluated based on at least one of the first data result and the second data result. The first evaluation submodule further includes: a first determining unit, configured to calculate the operational similarity between two target service units to be evaluated based on the first data result, wherein the operational similarity is used to characterize the similarity of the operational content corresponding to the two target service units to be evaluated; a second determining unit, configured to calculate the transaction similarity between the two target service units to be evaluated based on the second data result, wherein the transaction similarity is used to characterize the similarity of the processing procedures of the two target service units to be evaluated for transaction requests; and a first evaluation unit, configured to evaluate the combined value between the two target service units to be evaluated based on at least one of the operational similarity and the transaction similarity.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the system evaluation method according to any one of claims 1 to 5 when it is run.

8. An electronic device, characterized in that, The electronic device includes one or more processors; A memory for storing one or more programs, which, when executed by one or more processors, cause the one or more processors to be configured to run the programs, wherein the programs are configured to execute the system evaluation method as described in any one of claims 1 to 5 at runtime.

Images