Business processing method, business processing apparatus and computer-readable storage medium

Abstract

This application relates to a business processing method, a business processing apparatus, and a computer-readable storage medium. The method includes: receiving a business request sent by a front-end; determining a target version identifier based on the business request; obtaining identifiers and dependency identifiers of multiple target middlewares from a middleware database based on the target version identifier; determining a target execution order based on the dependency identifiers of the target middlewares, and generating a target identifier chain based on the identifiers of all target middlewares and the target execution order; and returning the target identifier chain to the front-end, enabling the front-end to call and execute middleware from the middleware database based on the target identifier chain. This method solves the problem in the prior art where mixing different versions of business code for the same business within the same code block leads to difficult code maintenance.

Description

Technical Field

[0001] This application relates to the field of business processing technology, and in particular to a business processing method, a business processing apparatus, and a computer-readable storage medium. Background Technology

[0002] As front-end functions become increasingly complex, modifications to front-end business processes have evolved from simple UI element changes (such as button colors) to complex, multi-step business processes (such as entirely new settlement processes or personalized information flow ordering). Furthermore, the same business process often has multiple versions to meet diverse user needs.

[0003] Currently, different versions of business code for the same business are mixed in the same code block using conditional statements. Developers directly use if / else, switch, and other conditional statements in the code block to hard-bind the business version identifier with the corresponding business code. When a user's business request is received, the branch conditional statement is triggered by identifying the version identifier of the requesting business, and then the specific version of the business code for that business is executed.

[0004] Because different versions of the same business code are mixed in the same code block through conditional statements, the structure of the code block will expand rapidly as the number of business versions increases. Furthermore, any subsequent modification to the business code of any version requires developers to delve into the core business code, which is not only difficult to maintain but also prone to triggering a chain of errors. Summary of the Invention

[0005] This application provides a business processing method, a business processing apparatus, and a computer-readable storage medium to solve the problem in the prior art where different versions of business code for the same business are mixed in the same code block, making the code difficult to maintain.

[0006] Firstly, this application provides a business processing method applied to a server, the server having a middleware database and an information database. The method includes: receiving a business request sent by a frontend, the business request representing a target user requesting a target business, the target business being configured with multiple versions; determining a target version identifier based on the business request, the target version identifier being the identifier of one of the multiple versions; and based on the target version identifier, obtaining identifiers and dependency identifiers of multiple target middlewares from the middleware database, each middleware in the middleware database being associated with at least one version identifier of a business. For middleware associated with the target version identifier, each middleware is a code module that implements a sub-business function, and the dependency identifier is the identifier of the middleware that the current middleware depends on. Based on the dependency identifier of the target middleware, the target execution order is determined, and based on the identifiers of all the target middlewares and the target execution order, a target identifier chain is generated, where the target execution order is the execution order of the plurality of target middlewares, and the target identifier chain includes the identifiers of the plurality of target middlewares sorted according to the target execution order. The target identifier chain is returned to the front end, so that the front end calls and executes the middleware from the middleware database based on the target identifier chain.

[0007] Optionally, the business request includes: the target user's profile data, which includes: multiple attribute identifiers and corresponding actual attribute values. The multiple attribute identifiers include at least: tag type, geographic location, device type, network type, and the identifier of the accessed page. Based on the business request, determining the target version identifier includes: obtaining the beta distribution corresponding to multiple first combinations from the information database. Each first combination consists of the identifier of one of the multiple versions and the profile data. The beta distribution corresponding to the first combination includes: a success parameter value and a failure parameter value. The success parameter value indicates that the user with the profile data is using... The corresponding version represents the cumulative number of times the preset business goal has been achieved. The failure parameter value represents the cumulative number of times a user with the profile data has failed to achieve the preset business goal when using the corresponding version. Random sampling is performed on the beta distribution corresponding to each of the first combinations to obtain multiple sample values. Each sample value corresponds one-to-one with the first combination. Each sample value represents the probability that a user with the profile data has achieved the preset business goal when using the corresponding version. The sample value is negatively correlated with the failure parameter value of the corresponding beta distribution and positively correlated with the success parameter value of the corresponding beta distribution. The identifier of the version corresponding to the largest sample value is determined as the target version identifier.

[0008] Optionally, after returning the target identifier chain to the front end, the method further includes: receiving a conversion value of the target identifier chain sent by the front end, wherein the conversion value includes: a first preset value and a second preset value, wherein the first preset value indicates that the preset business objective has been achieved, and the second preset value indicates that the preset business objective has not been achieved; when the conversion value is the first preset value, incrementing the success parameter value of the beta distribution corresponding to the target combination in the information database by one; when the conversion value is the second preset value, incrementing the failure parameter value of the beta distribution corresponding to the target combination by one; wherein the target combination consists of the target version identifier and the profile data.

[0009] Optionally, the business request includes: the profile data of the target user, the profile data including: multiple attribute identifiers and corresponding actual attribute values, the multiple attribute identifiers including at least: tag type, geographical location, device type, network type, and the identifier of the accessed page. After obtaining the identifiers and dependency identifiers of multiple target middlewares from the middleware database based on the target version identifier, before determining the target execution order based on the dependency identifiers of the target middlewares, and before generating a target identifier chain based on all the identifiers of the target middlewares and the target execution order, the method further includes: for each target middleware, based on the identifier of the target middleware, from... The information database is used to obtain the filtering rule data for the target middleware. The filtering rule data includes: attribute identifier, corresponding operation logic identifier, and corresponding target attribute value. The operation logic identifier represents the matching verification rule. For each target middleware, based on the attribute identifier of the filtering rule data, the corresponding actual attribute value is obtained from the profile data, and the target attribute value and the actual attribute value are matched and verified according to the corresponding operation logic identifier. If the matching verification passes, the identifier of the target middleware is retained; if the matching verification fails, the identifier of the target middleware is deleted from the identifiers of the plurality of target middlewares.

[0010] Optionally, after determining the target execution order based on the dependency identifiers of the target middleware, and generating a target identifier chain based on the identifiers of all the target middlewares and the target execution order, before returning the target identifier chain to the front end, the method further includes: for each target middleware in the target identifier chain, obtaining the execution result of the target middleware from the information database based on the identifier of the target middleware, and determining the failure rate of the target middleware based on the execution result of the target middleware, wherein the execution result includes: execution success or execution failure; deleting the identifiers of target middlewares in the target identifier chain that meet preset conditions, wherein the preset conditions are that the failure rate of the target middleware is not less than a preset failure rate.

[0011] Optionally, based on the dependency identifiers of the target middleware, the target execution order is determined, and a target identifier chain is generated based on the identifiers of all the target middlewares and the target execution order, including: determining multiple target execution orders based on the dependency identifiers of the target middlewares; combining the identifiers of the multiple target middlewares into multiple candidate identifier chains based on each target execution order, wherein each candidate identifier chain corresponds one-to-one with the target execution order, and each candidate identifier chain includes the identifiers of the multiple target middlewares sorted according to the corresponding target execution order; based on a second combination, obtaining the execution data of the corresponding candidate identifier chain from the information database, wherein the second combination includes: an identifier of one candidate identifier chain and the profile data, and the execution data includes at least: conversion value, execution time of each middleware, and execution result of each middleware, wherein the execution result includes: execution success and execution failure; determining the execution time, conversion rate, and failure rate of the candidate identifier chain based on the execution data of the candidate identifier chain; for each candidate identifier chain, based on the formula... Determine the comprehensive score for each of the candidate identifier chains, wherein, As the first weighting coefficient, This is the second weighting coefficient. This is the third weighting coefficient. The overall score for the candidate identifier chain, , The execution time of the candidate identifier chain. , The conversion rate of the candidate identifier chain. , The failure rate of the candidate identifier chain is used to determine the candidate identifier chain with the highest comprehensive score as the target identifier chain.

[0012] Secondly, this application provides a business processing method. The method has an application front-end and a server with a middleware database. The method includes: sending a business request to the server, wherein the business request represents a target user requesting a target business; receiving a target identifier chain sent by the server; and calling and executing middleware from the middleware database based on the target identifier chain.

[0013] Optionally, the business request includes: the profile data of the target user, the profile data including: multiple attribute identifiers and corresponding actual attribute values, the multiple attribute identifiers including at least: tag type, geographical location, device type, network type, and the identifier of the accessed page, the server having an information database, and in the process of calling and executing middleware from the middleware database based on the target identifier chain, the method includes: collecting the execution result of each target middleware in the target identifier chain, binding the identifier of the target middleware with the execution result of the target middleware and storing it in the information database, the execution result including: execution successful, execution failed; collecting the execution data of the target identifier chain, binding the identifier of the target identifier chain, the profile data and the execution data of the target identifier chain and storing it in the information database, the execution data including: conversion value, execution time of each target middleware, and execution result of each target middleware.

[0014] Thirdly, this application also provides a business processing apparatus, which is applied to a server. The server has a middleware database and an information database. The apparatus includes: a first receiving unit, configured to receive a business request sent by a front-end, wherein the business request represents a target user requesting a target business, and the target business is configured with multiple versions; a first determining unit, configured to determine a target version identifier based on the business request, wherein the target version identifier is the identifier of one of the multiple versions; and an obtaining unit, configured to obtain identifiers and dependency identifiers of multiple target middlewares from the middleware database based on the target version identifier, wherein each middleware in the middleware database is associated with at least one version identifier of a business. The target middleware is the middleware associated with the target version identifier, and each middleware is a code module that implements a sub-business function. The dependency identifier is the identifier of the middleware that the current middleware depends on. The second determining unit is used to determine the target execution order based on the dependency identifier of the target middleware, and to generate a target identifier chain based on the identifiers of all the target middleware and the target execution order. The target execution order is the execution order of the plurality of target middleware, and the target identifier chain includes the identifiers of the plurality of target middleware ordered according to the target execution order. The returning unit is used to return the target identifier chain to the front end, so that the front end calls and executes the middleware from the middleware database based on the target identifier chain.

[0015] Fourthly, this application also provides a computer storage medium storing computer-executable instructions for executing the business processing method described in any of the preceding claims of this application.

[0016] In this embodiment, compared to the prior art where different versions of business code for the same service are mixed in the same code block, this application splits the complete business code into multiple middleware with single functions. Each middleware corresponds to a sub-service and is stored as an independent code module in the middleware database. When a business request is received from the front end, the target version identifier corresponding to the target service is first determined. Then, based on the target version identifier, the identifiers of the middleware associated with the target version identifier and the dependency identifiers of these target middlewares are selected from the middleware database. Based on the dependency identifiers of the target middlewares, the execution order of these target middlewares is determined. According to the execution order of these target middlewares, the identifiers of these target middlewares are assembled into a target identifier chain and returned to the front end. The front end then calls and executes the middleware from the middleware database based on the target identifier chain. This achieves complete separation of different versions of business code for the same service, thereby solving the problem of difficult code maintenance caused by mixing different versions of business code for the same service in the same code block in the prior art. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0020] Figure 1 A flowchart illustrating a business processing method applied to a server, as provided in an embodiment of this application; Figure 2 A structural block diagram of the server provided in the embodiments of this application; Figure 3 A flowchart illustrating another business processing method applied to the server side, provided as an embodiment of this application; Figure 4 A flowchart illustrating a business processing method applied to a front-end, provided as an embodiment of this application; Figure 5 A schematic diagram of a business processing device applied to a server, provided in an embodiment of this application; Figure 6 This is a schematic diagram of a business processing device applied to the front end, provided as an embodiment of this application. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0022] The following disclosure provides numerous different embodiments or examples for implementing various structures of the invention. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of the invention. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0023] To address the technical problem in existing technologies where different versions of business code for the same business are mixed in the same code block, making the code difficult to maintain, this application provides a business processing method, a business processing device, and a computer-readable storage medium that can achieve complete separation of different versions of business code for the same business.

[0024] Figure 1 This is a flowchart illustrating a business processing method provided in an embodiment of this application. The method is applied to the server side, such as... Figure 2 As shown, the aforementioned server has an intelligent orchestration engine, a middleware database, and an information database. The aforementioned method is applied to the intelligent orchestration engine of the server, and the method includes: Step S101: Receive the business request sent by the front end; Among them, the above-mentioned business request represents the target user requesting the target business, and the above-mentioned target business is configured with multiple versions; Specifically, the target user is any one of multiple users, and the target business is any one of multiple businesses. The aforementioned business can be order creation, settlement payment, logistics freight calculation, etc. This application does not impose specific restrictions on the type of business.

[0025] Step S102: Based on the above business request, determine the target version identifier; The target version identifier mentioned above is the identifier of one of the multiple versions mentioned above; Specifically, each version has a globally unique identifier.

[0026] Step S103: Based on the target version identifier mentioned above, obtain the identifiers and dependency identifiers of multiple target middlewares from the middleware database. In this context, each middleware in the aforementioned middleware database is associated with at least one version identifier of a business, the aforementioned target middleware is the middleware associated with the aforementioned target version identifier, one of the aforementioned middlewares is a code module that implements a sub-business, and the aforementioned dependency identifier is the identifier of the middleware that the current middleware depends on. Specifically, each middleware identifier is globally unique.

[0027] Specifically, the complete business is broken down into multiple sub-businesses with single functions. The code modules of the sub-businesses are encapsulated as middleware. The same middleware can be used to implement different businesses. For example, if the sub-business is to obtain user information, the middleware for this sub-business can be used for settlement business or logistics business. The same middleware can be used to implement different versions of the same business. For example, if the sub-business is to obtain user information, the middleware for this sub-business can be used for simplified settlement business or complex settlement business. The simplified settlement business only includes core steps such as obtaining user information, obtaining product information, price calculation, address and product confirmation, and payment, while the complex settlement business adds steps such as coupon selection, points deduction, and selection of multiple payment methods.

[0028] Specifically, for the middleware that the current middleware depends on, for example, for the middleware of the price calculation sub-business, the process of obtaining product information must be executed before executing the middleware.

[0029] Specifically, the complete business code is broken down into multiple middleware with single functions. Each middleware corresponds to a sub-business and is stored as an independent code module in the middleware database. Different middleware can be used to implement different businesses or different versions of the same business, so that middleware can be reused across businesses and versions, which significantly improves development efficiency.

[0030] Step S104: Based on the dependency identifiers of the target middleware, determine the target execution order, and generate a target identifier chain based on the identifiers of all the target middleware and the target execution order. The execution order of the aforementioned targets is the execution order of the aforementioned multiple target middlewares, and the aforementioned target identifier chain includes the identifiers of the aforementioned multiple target middlewares ordered according to the aforementioned target execution order; Step S105: Return the target identifier chain to the front end, so that the front end can call and execute the middleware from the middleware database based on the target identifier chain.

[0031] Through the above embodiments, compared with the prior art of mixing different versions of business code for the same business in the same code block, this application splits the complete business code into multiple middleware with single functions. Each middleware corresponds to a sub-business and is stored as an independent code module in the middleware database. When a business request is received from the front end, the target version identifier corresponding to the target business is first determined. Then, based on the target version identifier, the identifiers of the middleware associated with the target version identifier and the dependency identifiers of these target middlewares are selected from the middleware database. Based on the dependency identifiers of the target middlewares, the execution order of these target middlewares is determined. According to the execution order of these target middlewares, the identifiers of these target middlewares are assembled into a target identifier chain and returned to the front end. The front end calls and executes the middleware from the middleware database based on the target identifier chain, thus realizing the complete separation of different versions of business code for the same business. This solves the problem of difficult code maintenance caused by mixing different versions of business code for the same business in the same code block in the prior art.

[0032] In an optional embodiment, the aforementioned service request includes: the profile data of the target user, the profile data including: multiple attribute identifiers and corresponding actual attribute values, the multiple attribute identifiers including at least: tag type, geographical location, device type, network type, and identifier of the accessed page, and the aforementioned step S102 can be implemented as follows: Step S1021: Obtain the beta distribution corresponding to multiple first combinations from the above information database. Each first combination consists of the identifier of one of the multiple versions and the above profile data. The beta distribution corresponding to the first combination includes: success parameter value and failure parameter value. The success parameter value represents the cumulative number of times a user with the above profile data has achieved the preset business goal when using the corresponding version. The failure parameter value represents the cumulative number of times a user with the above profile data has failed to achieve the preset business goal when using the corresponding version. Specifically, the aforementioned profile data includes: multiple attribute identifiers and corresponding actual attribute values. These multiple attribute identifiers include at least: tag type, geographic location, device type, network type, and the identifier of the accessed page. Among them, the actual attribute values ​​for the tag type include: ordinary user, VIP user; the actual attribute values ​​for the geographic location include: China, United States, etc.; the actual attribute values ​​for the device type are mobile phone, tablet, computer, etc.; the actual attribute values ​​for the network type are 2G, 3G, 4G, 5G, etc.; and the actual attribute values ​​for the identifier of the accessed page (which can be a URL path) are checkout (settlement page), user / center (user center page), etc.

[0033] Specifically, in the information database, the name of each service is bound to the identifiers of all versions of that service and stored therein. The service request includes the name of the target service, and based on the name of the target service, the identifiers of all versions of the target service are retrieved from the information database.

[0034] Specifically, in the information database, each first combination is bound to the beta distribution corresponding to that first combination and stored. Based on each of the first combinations, the beta distribution corresponding to the first combination is obtained from the information database. This application is to statistically analyze the beta distribution of the same portrait data and the same version.

[0035] Specifically, for example, in settlement transactions, the preset business objective can be to complete the payment.

[0036] Step S1022: Randomly sample the beta distribution corresponding to each of the first combinations to obtain multiple sampled values. Each sampled value corresponds to one of the first combinations. Each sampled value represents the probability that a user with the above profile data will achieve a preset business goal when using the corresponding version. Each sampled value is negatively correlated with the failure parameter value of the corresponding beta distribution and positively correlated with the success parameter value of the corresponding beta distribution. Step S1023: Determine the identifier of the version corresponding to the largest of the above sampled values ​​as the target version identifier.

[0037] In this embodiment, Thompson's sampling method from the multi-armed gambling machine algorithm is used. For each first combination (i.e., the identifier of each version of the target service and the profile data of the target user), a corresponding beta distribution Beta(α,β) is stored in the information database, where α is the success parameter value and β is the failure parameter value. Random sampling is performed on the beta distribution corresponding to each first combination to obtain the sampling value θ corresponding to the first combination. The sampling value θ is located in (0,1). The sampling value θ represents the probability that a user with the above profile data will achieve the preset business goal when using the corresponding version. Due to the characteristics of the beta distribution, the larger the success parameter value α, the larger the sampling value θ, and the larger the failure parameter value β, the smaller the sampling value θ (negative correlation). The identifier of the version corresponding to the largest sampling value is selected as the target version identifier, that is, the target service of the version corresponding to the largest sampling value is pushed to the target user to improve the achievement rate of the preset business goal. Furthermore, the actual performance of users with different profile data in achieving the preset business goal when using the same version may be different. Therefore, this application pushes versions based on the beta distribution of the same version with the same profile data, which further improves the achievement rate of the preset business goal.

[0038] In an optional embodiment, after step S105, the method includes: The conversion value of the target identifier chain sent by the front end is received. The conversion value includes a first preset value and a second preset value. The first preset value indicates that the preset business objective has been achieved, and the second preset value indicates that the preset business objective has not been achieved. When the conversion value is the first preset value, the success parameter value of the beta distribution corresponding to the target combination in the information database is incremented by one. When the conversion value is the second preset value, the failure parameter value of the beta distribution corresponding to the target combination is incremented by one. The target combination consists of the target version identifier and the profile data.

[0039] In this embodiment, based on the conversion value (first preset value and second preset value) of the target identifier chain, the success parameter value or failure parameter value of the beta distribution of the target combination is adjusted in real time. If the conversion value is the first preset value (the target user achieves the preset business goal by using the target version this time), the success parameter value of the beta distribution corresponding to the target combination is incremented by one, that is, the cumulative number of times the target user achieves the preset business goal by using the target version is incremented by one, thereby increasing the sampling value of the target combination corresponding to the next random sampling, thus increasing the probability of pushing the target version to the target user next time. If the conversion value is the second preset value (the target user does not achieve the preset business goal by using the target version this time), the failure parameter value of the beta distribution corresponding to the target combination is incremented by one, that is, the cumulative number of times the target user does not achieve the preset business goal by using the target version is incremented by one, thereby decreasing the sampling value of the target combination corresponding to the next random sampling, thus decreasing the probability of pushing the target version to the target user next time, thereby improving the achievement rate of the preset business goal.

[0040] In an optional embodiment, the aforementioned service request includes: the profile data of the target user, the profile data including: multiple attribute identifiers and corresponding actual attribute values, the multiple attribute identifiers including at least: tag type, geographical location, device type, network type, and identifier of the accessed page; after step S103 and before step S104, the method includes: For each of the above target middlewares, based on the identifier of the target middleware, the filtering rule data of the target middlewares is obtained from the above information database. The filtering rule data includes: attribute identifier, corresponding operation logic identifier and corresponding target attribute value. The operation logic identifier represents the matching verification rule. Specifically, in the information database, the identifier of each middleware is bound and stored with the filtering rule data of that middleware. The attribute identifiers in the filtering rule data include: tag type, geographical location, device type, network type, and the identifier of the accessed page.

[0041] For each of the above target middlewares, based on the attribute identifier of the above filtering rule data, the corresponding actual attribute value is obtained from the above profile data, and the target attribute value and the actual attribute value are matched and verified according to the corresponding operation logic identifier. If the matching verification passes, the identifier of the target middleware is retained; if the matching verification fails, the identifier of the target middleware is removed from the identifiers of the multiple target middlewares.

[0042] For example, the attribute identifier in the filtering rule data of the target middleware is a tag type, and the target attribute value of this attribute identifier is VIP user. The matching verification rule is equal to, that is, the target middleware is applicable to VIP users. It is determined whether the actual attribute value of the tag type in the profile data is equal to VIP user. If it is equal, the matching verification passes and the identifier of the target middleware is retained. If it is not included, the matching verification fails and the identifier of the target middleware is deleted. For example, the attribute identifier in the filtering rule data of the target middleware is a network type, and the target attribute value of this attribute identifier is 2G. The matching verification rule is not equal to, that is, the target middleware is applicable to network types other than 2G. It is determined whether the actual attribute value of the network type in the profile data is not equal to 2G. If it is not equal, the matching verification passes and the identifier of the target middleware is retained. If it is equal, the matching verification passes and the identifier of the target middleware is retained.

[0043] In this embodiment, for each target middleware, based on the attribute identifier of the filtering rule data, the corresponding actual attribute value is obtained from the profile data, and the target attribute value and the actual attribute value are matched and verified according to the corresponding operation logic identifier. If the matching verification passes, the identifier of the target middleware is retained; if the matching verification fails, the identifier of the target middleware is deleted from the identifiers of multiple target middlewares. This ensures that only the identifier of the target middleware that matches the profile data of the target user is retained, thereby improving the user experience and increasing the achievement rate of the preset business goals.

[0044] In an optional embodiment, after step S104 and before step S105, the method further includes: For each target middleware in the above target identification chain, based on the identifier of the target middleware, the execution result of the target middleware is obtained from the above information database, and based on the execution result of the target middleware, the failure rate of the target middleware is determined. The execution result includes: execution success and execution failure. Specifically, in the information database, the identifier of each middleware is bound and stored with the results of multiple executions of that middleware. Based on the identifier of the target middleware, the results of multiple executions of the target middleware are obtained from the information database. Based on the results of multiple executions of the target middleware, the failure rate of the target middleware is determined. For example, the failure rate of the target middleware is the percentage of the number of execution failures to the total number of executions.

[0045] Delete the identifiers of target middleware that meet the preset conditions in the above target identifier chain. The preset conditions are that the failure rate of the target middleware is not less than the preset failure rate.

[0046] In this embodiment, the identifiers of target middleware with a failure rate not less than a preset failure rate are deleted to avoid pushing these target middleware to target users, thereby reducing the probability of user operation failure and ensuring the reliability of target services.

[0047] In an optional embodiment, the aforementioned service request includes: the profile data of the target user, the profile data including: multiple attribute identifiers and corresponding actual attribute values, the multiple attribute identifiers including at least: tag type, geographical location, device type, network type, and identifier of the accessed page, and the aforementioned step S104 can be implemented as follows: Based on the dependency identifiers of the aforementioned target middleware, the execution order of multiple aforementioned targets is determined; Based on the execution order of the above targets, the identifiers of the above target middleware are combined into multiple candidate identifier chains. The candidate identifier chains correspond one-to-one with the execution order of the targets. The candidate identifier chains include the identifiers of the above target middleware sorted according to the corresponding target execution order. Based on the second combination, the execution data of the corresponding candidate identifier chain is obtained from the above information database. The second combination includes: an identifier of the above candidate identifier chain and the above profile data. The execution data includes at least: conversion value, execution time of each middleware, and execution result of each middleware. The execution result includes: execution success and execution failure. Based on the execution data of the above candidate identifier chains, determine the execution time, conversion rate, and failure rate of the above candidate identifier chains; Specifically, each identifier chain has a globally unique identifier. In the information database, each second combination is bound and stored with the execution data of multiple executions of the corresponding candidate identifier chain. Based on the second combination, the execution data of multiple executions of the corresponding candidate identifier chain is obtained from the information database. The execution time of the candidate identifier chain is the sum of the execution times in the multiple execution data. The conversion rate of the candidate identifier chain is the percentage of the conversion value with a first preset value in the multiple execution data to the total number of conversion values. The failure rate of the candidate identifier chain is the sum of the failure rates of each middleware in the candidate identifier chain. The calculation method for the failure rate of each middleware is the same as the calculation method for the failure rate of the middleware described above.

[0048] Specifically, the same version of the same service may be implemented using multiple identifier chains, and the target version of the target service may be implemented using multiple candidate identifier chains.

[0049] For each of the above candidate identifier chains, based on the formula Determine the comprehensive score for each of the above candidate identifier chains, where, As the first weighting coefficient, This is the second weighting coefficient. This is the third weighting coefficient. The overall score for the above candidate identifier chains, , The execution time of the above candidate identifier chains, , The conversion rate of the above candidate identifier chains, , The failure rate of the above candidate identifier chains; The candidate identifier chain with the highest overall score is determined as the target identifier chain.

[0050] In this embodiment, based on the dependency identifier of the target middleware, the execution order of multiple targets can be determined, thereby obtaining multiple candidate identifier chains. This application obtains a comprehensive score for the candidate identifier chains based on their execution time, conversion rate, and failure rate. The higher the comprehensive score of a candidate identifier chain, the shorter its execution time, the higher its conversion rate, and the lower its failure rate. This indicates that the candidate identifier chain executes faster, has a higher probability of achieving the preset business goal, and is more stable. Therefore, the candidate identifier chain with the highest comprehensive score is selected as the target identifier chain to improve the speed, goal achievement rate, and stability of the target business. Furthermore, the actual performance of users with different profile data using the same candidate identifier chain may differ in terms of execution time, achievement of preset business goals, and failure rate. Therefore, this application determines the comprehensive score based on the execution data of the same candidate identifier chain on the same profile data, further improving the speed, goal achievement rate, and stability of the target business.

[0051] Figure 3 This is a flowchart illustrating another business processing method provided in an embodiment of this application. The above method is applied to a server, such as... Figure 3 As shown, the above method includes: Receive business requests sent from the front end; Based on the target user profile data and the beta distribution corresponding to the identifier of each version of the target page (the first combination mentioned above), the multi-armed gambling machine algorithm is used to determine the target version identifier; Based on the target version identifier, retrieve the identifiers and dependency identifiers of multiple target middlewares from the middleware database; Determine whether the filtering rules data for each target middleware match the profile data of the target user; If a match is found, the identifier of the target middleware is retained; otherwise, the identifier of the target middleware is deleted. Based on the dependency identifiers of the aforementioned target middleware, multiple candidate identifier chains are generated; The candidate identifier chain with the highest overall score is identified as the target identifier chain. Determine if the failure rate of the target middleware is not less than the preset failure rate. If not, retain the target middleware's identifier; if yes, delete the target middleware's identifier. Return the target identifier chain to the front end; Receive the converted value of the target identifier chain sent by the front end; Based on the transformation value of the target identifier chain, adjust the parameter values ​​(success parameter value and failure parameter value) of the beta distribution corresponding to the target version identifier and the target user profile data.

[0052] Figure 4 This is a flowchart illustrating a business processing method provided in an embodiment of this application. The method is applied to the front end, such as... Figure 2 As shown, the server has an intelligent orchestration engine and a middleware database. The above methods include: Step S201: Send a service request to the aforementioned server. The service request represents the target user's request for the target service. Step S202: Receive the target identifier chain sent by the server. Specifically, the aforementioned target business configuration has multiple versions. The server is used to: determine the target version identifier based on the aforementioned business request, where the target version identifier is the identifier of one of the multiple versions; based on the target version identifier, retrieve the identifiers and dependency identifiers of multiple target middlewares from the middleware database, where each middleware in the middleware database is associated with at least one version identifier of a business, the target middleware is the middleware associated with the target version identifier, one of the middlewares is a code module that implements a sub-business, and the dependency identifier is the identifier of the middleware that the current middleware depends on; based on the dependency identifiers of the target middlewares, determine the target execution order, and generate a target identifier chain based on all the identifiers of the aforementioned target middlewares and the aforementioned target execution order, where the target execution order is the execution order of the aforementioned multiple target middlewares, and the target identifier chain includes the identifiers of the aforementioned multiple target middlewares sorted according to the aforementioned target execution order; and return the target identifier chain to the aforementioned frontend.

[0053] Step S203: Based on the target identifier chain, call and execute the middleware from the middleware database.

[0054] Through the above embodiments, compared with the prior art of mixing different versions of business code for the same business in the same code block, this application splits the complete business code into multiple middleware with single functions. Each middleware corresponds to a sub-business and is stored as an independent code module in the middleware database. When a business request is received from the front end, the target version identifier corresponding to the target business is first determined. Then, based on the target version identifier, the identifiers of the middleware associated with the target version identifier and the dependency identifiers of these target middlewares are selected from the middleware database. Based on the dependency identifiers of the target middlewares, the execution order of these target middlewares is determined. According to the execution order of these target middlewares, the identifiers of these target middlewares are assembled into a target identifier chain and returned to the front end. The front end calls and executes the middleware from the middleware database based on the target identifier chain, thus realizing the complete separation of different versions of business code for the same business. This solves the problem of difficult code maintenance caused by mixing different versions of business code for the same business in the same code block in the prior art.

[0055] In an optional embodiment, the aforementioned service request includes: the profile data of the target user, the profile data including: multiple attribute identifiers and corresponding actual attribute values, the multiple attribute identifiers including at least: tag type, geographical location, device type, network type, and identifier of the accessed page; during the aforementioned step S203, the method further includes: The execution results of each target middleware in the target identifier chain are collected, and the identifiers of the target middleware are bound to the execution results of the target middleware and stored in the information database. The execution results include: execution success and execution failure. Specifically, the front end binds the identifier of each target middleware with the execution results of the target middleware multiple times and stores them in the information database, so that the server can obtain the execution results of the target middleware multiple times from the information database based on the identifier of the target middleware.

[0056] The execution data of the aforementioned target identifier chain is collected, and the identifier of the aforementioned target identifier chain, the aforementioned profile data and the execution data of the aforementioned target identifier chain are bound and stored in the aforementioned information database. The aforementioned execution data includes: conversion value, execution time of each target middleware, and execution result of each target middleware.

[0057] Specifically, the identifier, profile data, and execution data of the identifier chain are bound together and stored in the information database, so that the server can obtain multiple execution data of the corresponding candidate identifier chain from the information database based on the second combination (the identifier of a candidate identifier chain and the profile data of the target user).

[0058] In an optional embodiment, during step S203, the method further includes: The converted value of the target identifier chain is sent to the server.

[0059] Specifically, the server receives the conversion value of the target identifier chain sent by the front end. When the conversion value is the first preset value, the server increments the success parameter value of the beta distribution corresponding to the target combination in the information database by one. When the conversion value is the second preset value, the server increments the failure parameter value of the beta distribution corresponding to the target combination by one. The target combination consists of the target version identifier and the profile data.

[0060] Figure 5 This application provides a business processing apparatus, which is applied to a server. The server has a middleware database and an information database, such as... Figure 5 As shown, the above-mentioned device includes: The first receiving unit 10 is used to receive a service request sent by the front end. The service request represents a target user requesting a target service. The target service is configured with multiple versions. The first determining unit 20 is used to determine a target version identifier based on the above-mentioned business request, wherein the target version identifier is the identifier of one of the above-mentioned multiple versions; The acquisition unit 30 is used to acquire the identifiers and dependency identifiers of multiple target middlewares from the middleware database based on the target version identifier. Each middleware in the middleware database is associated with at least one version identifier of a business. The target middleware is the middleware associated with the target version identifier. One of the middlewares is a code module that implements a sub-business. The dependency identifier is the identifier of the middleware that the current middleware depends on. The second determining unit 40 is used to determine the target execution order based on the dependency identifiers of the target middleware, and to generate a target identifier chain based on the identifiers of all the target middleware and the target execution order, wherein the target execution order is the execution order of the plurality of target middleware, and the target identifier chain includes the identifiers of the plurality of target middleware ordered according to the target execution order. Return unit 50 is used to return the target identifier chain to the front end, so that the front end can call and execute the middleware from the middleware database based on the target identifier chain.

[0061] In an optional embodiment, the aforementioned service request includes: the profile data of the target user, the profile data including: multiple attribute identifiers and corresponding actual attribute values, the multiple attribute identifiers including at least: tag type, geographical location, device type, network type, and identifier of the accessed page, and the aforementioned first determining unit is specifically used for: The beta distributions corresponding to multiple first combinations are obtained from the above information database. Each first combination consists of the identifier of one of the multiple versions and the above profile data. The beta distributions corresponding to the first combination include: success parameter values ​​and failure parameter values. The success parameter values ​​represent the cumulative number of times that users with the above profile data have achieved the preset business goals when using the corresponding version. The failure parameter values ​​represent the cumulative number of times that users with the above profile data have not achieved the preset business goals when using the corresponding version. Random sampling is performed on the beta distribution corresponding to each of the first combinations to obtain multiple sample values. Each sample value corresponds to one of the first combinations. Each sample value represents the probability that a user with the above profile data will achieve the preset business goal when using the corresponding version. Each sample value is negatively correlated with the failure parameter value of the corresponding beta distribution and positively correlated with the success parameter value of the corresponding beta distribution. The version corresponding to the largest of the above sampled values ​​is identified as the target version identifier.

[0062] In an optional embodiment, the above-described apparatus is further used for: The conversion value of the target identifier chain sent by the front end is received. The conversion value includes a first preset value and a second preset value. The first preset value indicates that the preset business objective has been achieved, and the second preset value indicates that the preset business objective has not been achieved. When the conversion value is the first preset value, the success parameter value of the beta distribution corresponding to the target combination in the information database is incremented by one. When the conversion value is the second preset value, the failure parameter value of the beta distribution corresponding to the target combination is incremented by one. The target combination consists of the target version identifier and the profile data.

[0063] In an optional embodiment, the aforementioned service request includes: the profile data of the target user, the profile data including: multiple attribute identifiers and corresponding actual attribute values, the multiple attribute identifiers including at least: tag type, geographic location, device type, network type, and identifier of the accessed page, and the aforementioned device is further used for: For each of the above target middlewares, based on the identifier of the target middleware, the filtering rule data of the target middlewares is obtained from the above information database. The filtering rule data includes: attribute identifier, corresponding operation logic identifier and corresponding target attribute value. The operation logic identifier represents the matching verification rule. For each of the above target middlewares, based on the attribute identifier of the above filtering rule data, the corresponding actual attribute value is obtained from the above profile data, and the target attribute value and the actual attribute value are matched and verified according to the corresponding operation logic identifier. If the matching verification passes, the identifier of the target middleware is retained; if the matching verification fails, the identifier of the target middleware is removed from the identifiers of the multiple target middlewares.

[0064] In an optional embodiment, the above-described apparatus is further used for: For each target middleware in the above target identification chain, based on the identifier of the target middleware, the execution result of the target middleware is obtained from the above information database, and based on the execution result of the target middleware, the failure rate of the target middleware is determined. The execution result includes: execution success and execution failure. Delete the identifiers of target middleware that meet the preset conditions in the above target identifier chain. The preset conditions are that the failure rate of the target middleware is not less than the preset failure rate.

[0065] In an optional embodiment, the second determining unit described above is used for: Based on the dependency identifiers of the aforementioned target middleware, the execution order of multiple aforementioned targets is determined; Based on the execution order of the above targets, the identifiers of the above target middleware are combined into multiple candidate identifier chains. The candidate identifier chains correspond one-to-one with the execution order of the targets. The candidate identifier chains include the identifiers of the above target middleware sorted according to the corresponding target execution order. Based on the second combination, the execution data of the corresponding candidate identifier chain is obtained from the above information database. The second combination includes: an identifier of the above candidate identifier chain and the above profile data. The execution data includes at least: conversion value, execution time of each middleware, and execution result of each middleware. The execution result includes: execution success and execution failure. Based on the execution data of the above candidate identifier chains, determine the execution time, conversion rate, and failure rate of the above candidate identifier chains; For each of the above candidate identifier chains, based on the formula Determine the comprehensive score for each of the above candidate identifier chains, where, As the first weighting coefficient, This is the second weighting coefficient. This is the third weighting coefficient. The overall score for the above candidate identifier chains, , The execution time of the above candidate identifier chains, , The conversion rate of the above candidate identifier chains, , The failure rate of the above candidate identifier chains; The candidate identifier chain with the highest overall score is determined as the target identifier chain.

[0066] Figure 6 This application provides a business processing apparatus, wherein the apparatus has an application front-end and a server-side middleware database, such as... Figure 6 As shown, the above-mentioned device includes: Sending unit 60 is used to send a service request to the aforementioned server, wherein the service request represents a target user requesting a target service; The second receiving unit 70 is used to receive the target identifier chain sent by the server. Calling unit 80 is used to call and execute middleware from the middleware database based on the target identifier chain.

[0067] In an optional embodiment, the aforementioned business request includes: the profile data of the target user, the profile data including: multiple attribute identifiers and corresponding actual attribute values, the multiple attribute identifiers including at least: tag type, geographical location, device type, network type, and identifier of the accessed page, the aforementioned server having an information database, and the aforementioned device further used for: The execution results of each target middleware in the target identifier chain are collected, and the identifiers of the target middleware are bound to the execution results of the target middleware and stored in the information database. The execution results include: execution success and execution failure. The execution data of the aforementioned target identifier chain is collected, and the identifier and profile data of the aforementioned target identifier chain are bound with the execution data of the aforementioned target identifier chain and stored in the aforementioned information database. The aforementioned execution data includes: conversion value, execution time of each target middleware, and execution result of each target middleware.

[0068] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the business processing method provided in any of the foregoing method embodiments.

[0069] The device embodiments described above are merely illustrative. 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 network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0070] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0071] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0072] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A business processing method, characterized in that, The method is applied to a server, which has a middleware database and an information database. The method includes: Receive a business request sent from the front end. The business request represents a target user requesting a target service. The target service is configured with multiple versions. Based on the business request, a target version identifier is determined, wherein the target version identifier is the identifier of one of the multiple versions; Based on the target version identifier, the identifiers and dependency identifiers of multiple target middlewares are obtained from the middleware database. Each middleware in the middleware database is associated with at least one version identifier of a business. The target middleware is the middleware associated with the target version identifier. Each middleware is a code module that implements a sub-business. The dependency identifier is the identifier of the middleware that the current middleware depends on. Based on the dependency identifiers of the target middleware, the target execution order is determined, and based on the identifiers of all the target middlewares and the target execution order, a target identifier chain is generated, wherein the target execution order is the execution order of the plurality of target middlewares, and the target identifier chain includes the identifiers of the plurality of target middlewares sorted according to the target execution order; The target identifier chain is returned to the front end, so that the front end can call and execute the middleware from the middleware database based on the target identifier chain.

2. The method according to claim 1, characterized in that, The business request includes: the target user's profile data, which includes: multiple attribute identifiers and corresponding actual attribute values. The multiple attribute identifiers include at least: tag type, geographic location, device type, network type, and the identifier of the accessed page. Based on the business request, a target version identifier is determined, including: The beta distributions corresponding to multiple first combinations are obtained from the information database. Each first combination consists of an identifier of one of the multiple versions and the profile data. The beta distribution corresponding to the first combination includes a success parameter value and a failure parameter value. The success parameter value represents the cumulative number of times a user with the profile data achieves a preset business goal when using the corresponding version. The failure parameter value represents the cumulative number of times a user with the profile data fails to achieve the preset business goal when using the corresponding version. Random sampling is performed on the beta distribution corresponding to each of the first combinations to obtain multiple sampled values. Each sampled value corresponds one-to-one with the first combination. Each sampled value represents the probability that a user with the profile data will achieve a preset business goal when using the corresponding version. Each sampled value is negatively correlated with the failure parameter value of the corresponding beta distribution and positively correlated with the success parameter value of the corresponding beta distribution. The identifier of the version corresponding to the largest sample value is determined as the target version identifier.

3. The method according to claim 2, characterized in that, After returning the target identifier chain to the front end, the method further includes: The system receives the conversion value of the target identifier chain sent by the front end. The conversion value includes a first preset value and a second preset value. The first preset value indicates that the preset business objective has been achieved, and the second preset value indicates that the preset business objective has not been achieved. When the conversion value is the first preset value, the success parameter value of the beta distribution corresponding to the target combination in the information database is incremented by one. When the conversion value is the second preset value, the failure parameter value of the beta distribution corresponding to the target combination is incremented by one. The target combination consists of the target version identifier and the profile data.

4. The method according to claim 1, characterized in that, The business request includes: the target user's profile data, which includes: multiple attribute identifiers and corresponding actual attribute values. The multiple attribute identifiers include at least: tag type, geographic location, device type, network type, and the identifier of the accessed page. After obtaining the identifiers and dependency identifiers of multiple target middlewares from the middleware database based on the target version identifier, and before determining the target execution order based on the dependency identifiers of the target middlewares, and before generating a target identifier chain based on all the identifiers of the target middlewares and the target execution order, the method further includes: For each target middleware, based on the identifier of the target middleware, the filtering rule data of the target middleware is obtained from the information database. The filtering rule data includes: attribute identifier, corresponding operation logic identifier and corresponding target attribute value. The operation logic identifier represents the matching verification rule. For each target middleware, based on the attribute identifier of the filtering rule data, the corresponding actual attribute value is obtained from the profile data, and the target attribute value and the actual attribute value are matched and verified according to the corresponding operation logic identifier. If the matching verification passes, the identifier of the target middleware is retained; if the matching verification fails, the identifier of the target middleware is deleted from the identifiers of the plurality of target middlewares.

5. The method according to claim 1, characterized in that, After determining the target execution order based on the dependency identifiers of the target middleware, and generating a target identifier chain based on the identifiers of all the target middlewares and the target execution order, before returning the target identifier chain to the front end, the method further includes: For each target middleware in the target identifier chain, based on the identifier of the target middleware, the execution result of the target middleware is obtained from the information database, and based on the execution result of the target middleware, the failure rate of the target middleware is determined. The execution result includes: execution successful or execution failed. Delete the identifiers of target middleware that meet the preset conditions in the target identifier chain. The preset conditions are that the failure rate of the target middleware is not less than the preset failure rate.

6. The method according to claim 2 or 3, characterized in that, Based on the dependency identifiers of the target middleware, the target execution order is determined, and based on the identifiers of all the target middleware and the target execution order, a target identifier chain is generated, including: Based on the dependency identifiers of the target middleware, the execution order of the multiple targets is determined; Based on the execution order of each target, the identifiers of the plurality of target middlewares are combined into a plurality of candidate identifier chains, each candidate identifier chain corresponding one-to-one with the target execution order, and each candidate identifier chain includes the identifiers of the plurality of target middlewares sorted according to the corresponding target execution order; Based on the second combination, the execution data of the corresponding candidate identifier chain is obtained from the information database. The second combination includes: an identifier of the candidate identifier chain and the profile data. The execution data includes at least: conversion value, execution time of each middleware, and execution result of each middleware. The execution result includes: execution success and execution failure. Based on the execution data of the candidate identifier chain, determine the execution time, conversion rate, and failure rate of the candidate identifier chain; For each of the candidate identifier chains, based on the formula Determine the comprehensive score for each of the candidate identifier chains, wherein, As the first weighting coefficient, This is the second weighting coefficient. This is the third weighting coefficient. The overall score for the candidate identifier chain, , The execution time of the candidate identifier chain. , The conversion rate of the candidate identifier chain. , The failure rate of the candidate identifier chain; The candidate identifier chain with the highest comprehensive score is determined as the target identifier chain.

7. A business processing method, characterized in that, The method is applied to the front end, and the server has a middleware database. The method includes: Send a service request to the server, wherein the service request represents a target user requesting a target service; Receive the target identifier chain sent by the server; The middleware is invoked and executed from the middleware database based on the target identifier chain.

8. The method according to claim 7, characterized in that, The business request includes: the target user's profile data, which includes: multiple attribute identifiers and corresponding actual attribute values. The multiple attribute identifiers include at least: tag type, geographic location, device type, network type, and the identifier of the accessed page. The server has an information database. During the process of calling and executing middleware from the middleware database based on the target identifier chain, the method includes: The execution result of each target middleware in the target identifier chain is collected, and the identifier of the target middleware is bound to the execution result of the target middleware and stored in the information database. The execution result includes: execution successful and execution failed. The execution data of the target identifier chain is collected, and the identifier and profile data of the target identifier chain are bound to the execution data of the target identifier chain and stored in the information database. The execution data includes: conversion value, execution time of each target middleware, and execution result of each target middleware.

9. A business processing device, characterized in that, The device is applied to a server, the server having a middleware database and an information database, and the device includes: The first receiving unit is used to receive a service request sent by the front end. The service request represents a target user requesting a target service, and the target service is configured with multiple versions. The first determining unit is configured to determine a target version identifier based on the service request, wherein the target version identifier is an identifier of one of the plurality of versions; The acquisition unit is used to acquire the identifiers and dependency identifiers of multiple target middlewares from the middleware database based on the target version identifier. Each middleware in the middleware database is associated with at least one version identifier of a business. The target middleware is the middleware associated with the target version identifier. Each middleware is a code module that implements a sub-business. The dependency identifier is the identifier of the middleware that the current middleware depends on. The second determining unit is configured to determine the target execution order based on the dependency identifiers of the target middleware, and generate a target identifier chain based on the identifiers of all the target middlewares and the target execution order, wherein the target execution order is the execution order of the plurality of target middlewares, and the target identifier chain includes the identifiers of the plurality of target middlewares sorted according to the target execution order; The return unit is used to return the target identifier chain to the front end, so that the front end can call and execute the middleware from the middleware database based on the target identifier chain.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the business processing method as described in any one of claims 1 to 6, or implements the steps of the business processing method as described in any one of claims 7 to 8.

Images