Publishing method, device, storage medium and electronic device of financial service system

Abstract

The present invention discloses a publishing method, device, storage medium and electronic device for a financial service system. It relates to the field of financial technology or other related technical fields. The method comprises: in the process of publishing a target version of a service system, locating the current publishing stage, receiving a transaction request, and searching for a routing rule that matches the transaction request to obtain a target routing rule; based on the target routing rule, forwarding the transaction request to a target server in a server cluster, wherein the target server is used to process the transaction request; based on the processing result of the transaction request, verifying whether there is an abnormality in the target version of the service system; if the verification result indicates that there is no abnormality in the target version of the service system, entering the next publishing stage, until N publishing stages are completed. The present invention solves the technical problem of poor publishing effect of a new version of a business service system in the related art.

Description

Technical Field

[0001] The present invention relates to the field of financial technology or other related technical fields, and in particular to a publishing method, device, storage medium and electronic device for a financial service system. Background Art

[0002] Against the backdrop of increasingly stringent securities business regulation, the stability of financial institutions' securities business systems has received high attention from regulatory authorities at all levels. Accurately controlling the scope of fault impact while ensuring the iterative launch of business services and ensuring the stability of banks' securities business systems is an urgent issue that needs to be addressed.

[0003] Currently, the grayscale release method for securities business systems of financial institutions mainly involves deploying the new version of business services on grayscale cluster servers. All business transaction requests are randomly routed and processed by the new version of business services and the old version of business services respectively. The business results are verified by checking the execution results of the new version of business services. After the verification is passed, the new version of business services are directly deployed to all servers to complete the business service online.

[0004] As the frequency of user transactions increases, the stability requirements of financial institutions' securities business systems are becoming increasingly higher. However, random routing is used by the new version business service and the old version business service to process transaction requests separately. Failures in the new version business service may not be discovered. After verification, the new version business service is deployed to all servers. Once a failure in the new version business service is discovered, the impact is wide-ranging and difficult to resolve quickly, resulting in the securities business system being unable to provide services to customers.

[0005] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0006] Embodiments of the present invention provide a publishing method, apparatus, storage medium, and electronic device for a financial service system, to at least solve the technical problem in related technologies of poor publishing effects of new versions of business service systems.

[0007] According to one aspect of an embodiment of the present invention, a publishing method for a financial service system is provided, comprising: in a publishing process for a target version of the service system, locating a current publishing stage, receiving a transaction request, and searching for a routing rule that matches the transaction request to obtain a target routing rule, wherein the publishing process for the target version of the service system includes N publishing stages, and in each of the publishing stages, the number of servers in a server cluster deploying the target version of the service system is higher than that in the previous publishing stage, and the target routing rule is used to determine a forwarding address for the transaction request, where N is a positive integer; based on the target routing rule, forwarding the transaction request to a target server in the server cluster, wherein the target server is used to process the transaction request to obtain a processing result of the transaction request; based on the processing result, verifying whether there is an abnormality in the target version of the service system to obtain a verification result; and if the verification result indicates that there is no abnormality in the target version of the service system, entering the next publishing stage, until the N publishing stages are completed.

[0008] Furthermore, based on the processing result, it is verified whether there is any abnormality in the service system of the target version to obtain a verification result, including: obtaining a preset verification script, and executing the preset verification script to verify whether the processing result is consistent with the expected result; when the processing result is consistent with the expected result, it is determined that the verification result indicates that there is no abnormality in the service system of the target version; when the processing result is inconsistent with the expected result, it is determined that the verification result indicates that there is an abnormality in the service system of the target version.

[0009] Furthermore, in the process of publishing the target version of the service system, it also includes: obtaining the parameter data filled in the target page, and generating routing rules corresponding to the parameter data, wherein the target page is used to configure the parameters of the routing rules; storing the routing rules corresponding to the parameter data in the target storage space.

[0010] Furthermore, searching for a routing rule that matches the transaction request to obtain a target routing rule includes: reading the routing rules stored in the target storage space to obtain S routing rules, where S is a positive integer greater than 1; matching the transaction data carried in the transaction request with the S routing rules, and determining the routing rule that matches the transaction data as the target routing rule.

[0011] Furthermore, when the verification result indicates that there is an abnormality in the service system of the target version, it rolls back to the specified release stage and generates an early warning message, wherein the early warning message is used to prompt the target object that there is a fault in the service system of the target version in the current release stage, and the specified release stage includes: the release stage before the current release stage; the early warning message is sent to the device used by the target object.

[0012] Furthermore, based on the target routing rule, forwarding the transaction request to the target server in the server cluster includes: parsing the target routing rule based on the data format of the target routing rule to obtain a forwarding address of the transaction request; and forwarding the transaction request to the target server based on the forwarding address of the transaction request.

[0013] Furthermore, when the verification result indicates that there is no abnormality in the target version of the service system, after entering the next release stage, it also includes: obtaining the release strategy of the target version of the service system in the next release stage, wherein the release strategy at least includes: in the next release stage, the number of servers of the target version of the service system deployed in the server cluster; based on the release strategy, deploying the target version of the service system in the server cluster.

[0014] According to another aspect of an embodiment of the present invention, a publishing device for a financial service system is also provided, including: a first processing unit, used to locate the current publishing stage, receive a transaction request, and find a routing rule matching the transaction request during the publishing process of a target version of the service system to obtain a target routing rule, wherein the publishing process of the target version of the service system includes N publishing stages, and in each of the publishing stages, the number of servers deploying the target version of the service system in the server cluster is higher than that in the previous publishing stage, and the target routing rule is used to determine the forwarding address of the transaction request, where N is a positive integer; a forwarding unit, used to forward the transaction request to a target server in the server cluster based on the target routing rule, wherein the target server is used to process the transaction request and obtain a processing result of the transaction request; a verification unit, used to verify whether there is an abnormality in the target version of the service system based on the processing result to obtain a verification result; a second processing unit, used to enter the next publishing stage if the verification result indicates that there is no abnormality in the target version of the service system, until N of the publishing stages are completed.

[0015] Furthermore, the verification unit includes: a verification sub-unit, used to obtain a preset verification script and execute the preset verification script to verify whether the processing result is consistent with the expected result; a first determination sub-unit, used to determine that the verification result indicates that there is no abnormality in the target version of the service system when the processing result is consistent with the expected result; and a second determination sub-unit, used to determine that the verification result indicates that there is an abnormality in the target version of the service system when the processing result is inconsistent with the expected result.

[0016] Furthermore, the publishing device of the financial service system also includes: a first acquisition unit, used to obtain the parameter data filled in the target page during the publishing process of the target version of the service system, and generate routing rules corresponding to the parameter data, wherein the target page is used to configure the parameters of the routing rules; a storage unit, used to store the routing rules corresponding to the parameter data to the target storage space.

[0017] Furthermore, the first processing unit includes: a reading subunit, used to read the routing rules stored in the target storage space to obtain S routing rules, where S is a positive integer greater than 1; a matching subunit, used to match the transaction data carried in the transaction request with the S routing rules, and determine the routing rule that matches the transaction data as the target routing rule.

[0018] Furthermore, the publishing device of the financial service system also includes: a rollback unit, which is used to roll back to a specified publishing stage and generate an early warning message when the verification result indicates that there is an abnormality in the target version of the service system, wherein the early warning message is used to prompt the target object that there is a fault in the target version of the service system in the current publishing stage, and the specified publishing stage includes: a publishing stage before the current publishing stage; a sending unit, which is used to send the early warning message to the device used by the target object.

[0019] Furthermore, the forwarding unit includes: a parsing subunit, which is used to parse the target routing rule based on the data format of the target routing rule to obtain the forwarding address of the transaction request; and a forwarding subunit, which is used to forward the transaction request to the target server based on the forwarding address of the transaction request.

[0020] Furthermore, the publishing device of the financial service system also includes: a second acquisition unit, which is used to obtain the publishing strategy of the target version of the service system in the next publishing stage after entering the next publishing stage when the verification result indicates that there is no abnormality in the target version of the service system, wherein the publishing strategy at least includes: the number of servers of the target version of the service system deployed in the server cluster in the next publishing stage; and a deployment unit, which is used to deploy the target version of the service system in the server cluster based on the publishing strategy.

[0021] According to another aspect of an embodiment of the present invention, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned publishing methods of the financial service system by executing the executable instructions.

[0022] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, which stores a computer program, wherein when the computer program runs, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned methods for publishing a financial service system.

[0023] In the present invention, during the release process of a target version of a service system, the current release stage is located, a transaction request is received, and a routing rule matching the transaction request is searched to obtain a target routing rule. The release process of the target version of the service system includes N release stages. In each release stage, the number of servers in a server cluster deploying the target version of the service system is higher than in the previous release stage. The target routing rule is used to determine a forwarding address for the transaction request, where N is a positive integer. Based on the target routing rule, the transaction request is forwarded to a target server in the server cluster. The target server is used to process the transaction request and obtain a processing result of the transaction request. Based on the processing result, whether the target version of the service system has an anomaly is verified to obtain a verification result. If the verification result indicates that the target version of the service system has no anomaly, the next release stage is entered, and the process continues until the N release stages are completed. This solves the technical problem of poor release results of new versions of business service systems in related technologies.

[0024] In the present invention, the target version of the service system is gradually deployed to the server cluster through multiple release stages, and in each release stage, the transaction request is forwarded to the corresponding server for processing through pre-defined routing rules. This avoids the situation in the related art where the new version of the service system is directly deployed to all servers after verification when gray release is adopted, which leads to a wide range of impact after a failure occurs. This achieves the technical effect of reducing the impact range of failures and improving the stability of system releases when releasing a new version of the business service system. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0026] Figure 1 is a flow chart of an optional publishing method of a financial service system according to an embodiment of the present invention;

[0027] Figure 2 is a structural diagram of a publishing system of an optional financial service system according to an embodiment of the present invention;

[0028] Figure 3 is a schematic diagram of the internal structure of an optional data acquisition device 1 according to an embodiment of the present invention;

[0029] Figure 4 is a schematic diagram of the structure of an optional transaction routing rule configuration device 2 according to an embodiment of the present invention;

[0030] Figure 5 is a schematic diagram of the internal structure of an optional routing rule loading device 3 according to an embodiment of the present invention;

[0031] Figure 6 This is a schematic diagram of the internal structure of an optional business service result verification device 4 according to an embodiment of the present invention;

[0032] Figure 7 is a schematic diagram of the internal structure of an optional transaction routing strategy updating device 5 according to an embodiment of the present invention;

[0033] Figure 8 This is a schematic diagram of the internal structure of an optional service version rolling update strategy device 6 according to an embodiment of the present invention;

[0034] Figure 9 is a schematic diagram of the internal structure of an optional result notification device 7 according to an embodiment of the present invention;

[0035] Figure 10 is a schematic diagram of the internal structure of an optional event alarm device 8 according to an embodiment of the present invention;

[0036] Figure 11 is a schematic diagram of an optional publishing device of a financial service system according to an embodiment of the present invention;

[0037] Figure 12 is a schematic diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0038] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0039] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0040] It should be noted that the publishing method, device, storage medium and electronic device of the financial service system in the present disclosure can be used in the financial technology field when a new version of the system is released, and can also be used in any field other than the financial technology field. In the case of a new version of the system, the application field of the publishing method, device, storage medium and electronic device of the financial service system in the present disclosure is not limited.

[0041] It should be noted that the user information (including but not limited to user device information, user personal information, etc.), collected information and data (including but not limited to data used for analysis, stored data, displayed data, electronic medical records, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good customs, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0042] The present invention can be applied to various software products, control systems, and client (including but not limited to: mobile clients, PCs, etc.) control systems of various financial institutions. Taking software products as an example for illustration, by installing a new version of the software product on a mobile client, the business content of the financial institution (including but not limited to: transfer, financial management, funds, payment, account checking, advertising, recommendation and other business functions) can be realized through the new version of the software product.

[0043] Example 1

[0044] According to an embodiment of the present invention, a method embodiment of an optional publishing method of a financial services system is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0045] Figure 1 FIG. 1 is a flow chart of an optional publishing method of a financial service system according to an embodiment of the present invention. Figure 1 As shown, the method includes the following steps:

[0046] Step S101 , during the release process of the target version of the service system, locate the current release stage, receive a transaction request, and search for a routing rule matching the transaction request to obtain a target routing rule.

[0047] The release process of the target version of the service system includes N release stages. In each release stage, the number of servers deploying the target version of the service system in the server cluster is higher than that in the previous release stage. The target routing rule is used to determine the forwarding address of the transaction request, and N is a positive integer.

[0048] The above-mentioned service system may include a system for processing transaction data in a financial institution, including but not limited to: a securities business system. The target version of the service system may refer to a new version of the service system obtained by upgrading and transforming certain service functions in the old version of the service system.

[0049] To avoid deploying the new version of the business service on a grayscale cluster server, as in related technologies, all business transaction requests are randomly routed and handled by the new version and the old version of the business service, respectively. After verification, the new version of the business service is directly deployed to all servers to complete the business service launch. In the event of a failure with a wide impact, in this embodiment, the process of releasing the target version of the service system can include multiple release phases. The deployment of the new version of the service system in the server cluster can vary between release phases. For example, in each release phase, the number of servers deployed with the target version of the service system in the server cluster can be higher than in the previous release phase. In an optional example, different routing rules can be set for different release phases, and the corresponding traffic of transaction requests flowing into the target version of the service system and the old version of the service system can also be different. This achieves the purpose of rolling upgrades of the service system and improves the stability of the release of the new version of the service system.

[0050] The above-mentioned routing rules can be used to determine the address to which transaction requests corresponding to the business of the financial institution are forwarded. For example, according to the routing rules, transaction requests containing preset data can be forwarded to a server with a target version of the service system deployed. The preset data may include but is not limited to: a mobile phone number with certain digits consisting of xx digits, an account number with certain digits consisting of xx data, etc.

[0051] Step S102: forwarding the transaction request to a target server in the server cluster based on the target routing rule, wherein the target server is used to process the transaction request and obtain a processing result of the transaction request.

[0052] In this embodiment, the target routing rule can be parsed to identify the forwarding address of the transaction request (ie, the address of the target server), and then the transaction request is forwarded to the target server in the server cluster for processing based on the forwarding address.

[0053] Step S103: Based on the processing result, verify whether there is any abnormality in the service system of the target version, and obtain a verification result.

[0054] In this embodiment, it is also possible to verify whether the processing result meets expectations, thereby determining whether there is an abnormality in the service system of the target version of the current release stage, and obtaining a verification result.

[0055] Step S104: If the verification result indicates that there is no abnormality in the target version of the service system, the system proceeds to the next release phase until N release phases are completed.

[0056] When the verification result indicates that there is no abnormality in the target version of the service system, the next release phase is entered. In the next release phase, the deployment of the target version of the service system in the server cluster can be adjusted according to the verification result, and the routing rules can also be different from the current release phase.

[0057] When the verification result indicates that there is an abnormality in the target version of the service system, it is also possible to roll back to the specified release stage. The specified release stage may refer to the release stage before the current release stage, thereby achieving the technical effect of improving the flexibility of adjusting the grayscale range of the release of the new version of the service system.

[0058] Through the above steps, in this embodiment, the target version of the service system is gradually deployed to the server cluster through multiple release stages. In each release stage, transaction requests are forwarded to the corresponding server for processing using pre-defined routing rules. This avoids the situation in related technologies where a new version of the service system is directly deployed to all servers after verification during a grayscale release, which can have a wide impact if a failure occurs. This achieves the technical effect of reducing the impact of failures and improving the stability of system releases when releasing a new version of the business service system. This further solves the technical problem of poor release performance of new versions of business service systems in related technologies.

[0059] Optionally, based on the processing result, verify whether there is any abnormality in the target version of the service system to obtain a verification result, including: obtaining a preset verification script, and executing the preset verification script to verify whether the processing result is consistent with the expected result; when the processing result is consistent with the expected result, determine that the verification result indicates that there is no abnormality in the target version of the service system; when the processing result is inconsistent with the expected result, determine that the verification result indicates that there is an abnormality in the target version of the service system.

[0060] In this embodiment, the preset verification rules can be obtained, the verification rules can be parsed, the corresponding automated verification script (corresponding to the preset verification script) can be obtained, the automated verification script can be executed, the verification results can be obtained and stored. The following processing can be performed based on the verification results of the automated verification script:

[0061] Result 1: The verification result of the verification script indicates that the processing result of the transaction request is consistent with the expected result, indicating that there is no abnormality in the new version of the business service (that is, there is no abnormality in the target version of the service system). The business service expansion grayscale strategy for the next release phase can be obtained according to the preset business service grayscale strategy. Among them, the business service expansion grayscale strategy for the next release phase can refer to expanding the deployment scope of the target version of the service system in the server cluster.

[0062] Result 2: The verification script's verification result indicates that the transaction request processing result is inconsistent with expectations, indicating that the new version of the business service has a fault (that is, there is an anomaly in the target version of the service system). You can obtain a business service rollback grayscale policy according to the business service grayscale policy.

[0063] By presetting verification scripts, it is possible to automatically verify whether the processing results of transaction requests are consistent with expectations, thereby achieving the technical effect of improving the verification efficiency of the processing results of the new version of the business service.

[0064] Optionally, during the release of the target version of the service system, it also includes: obtaining the parameter data filled in the target page and generating routing rules corresponding to the parameter data, wherein the target page is used to configure the parameters of the routing rules; storing the routing rules corresponding to the parameter data in the target storage space.

[0065] In order to improve the flexibility of routing rule settings, the parameters of routing rules can also be configured using the target page. By real-time monitoring of whether new parameter data is set on the target page, if new parameter data is set, the parameter data filled in the target page can be obtained, and the parameter data can be converted into a specified format to obtain the routing rules corresponding to the parameter data. The routing rules corresponding to the parameter data are stored in the target storage space, thereby achieving the purpose of flexibly adjusting routing rules during the release of the target version of the service system.

[0066] For example, it is possible to detect in real time whether there are any new routing rules to be implemented, and mark the routing policies to be implemented as effective. Then, the routing rules that have not been loaded and marked as effective can be loaded and stored in the target storage space so that subsequent business transaction requests can be forwarded according to the new routing rules.

[0067] Optionally, searching for a routing rule that matches the transaction request to obtain a target routing rule includes: reading the routing rules stored in the target storage space to obtain S routing rules, where S is a positive integer greater than 1; matching the transaction data carried in the transaction request with the S routing rules, and determining the routing rule that matches the transaction data as the target routing rule.

[0068] In this embodiment, the routing rules stored in the target storage space can also be read, and the transaction data carried in the transaction request is matched with the read routing rules, and the successfully matched routing rules are determined as the target routing rules. For example, if the customer number indicated in the transaction data is 0010000, and the forwarding address corresponding to the first three digits of the customer number 001 indicated in the routing rule is the forwarding address of the target server, then the transaction data is successfully matched with the routing rule, achieving the purpose of controlling the routing of the transaction request and realizing the technical effect of controlling the scope of influence of the failure of the new version of the service system.

[0069] Optionally, if the verification result indicates that there is an abnormality in the service system of the target version, it will roll back to the specified release stage and generate an early warning message, wherein the early warning message is used to prompt the target object that there is a fault in the service system of the target version in the current release stage, and the specified release stage includes: the release stage before the current release stage; the early warning message is sent to the device used by the target object.

[0070] In this embodiment, when the verification result indicates that there is an abnormality in the target version of the service system, the current release stage can be rolled back to the specified release stage according to the pre-set rollback strategy, and an early warning message can be generated. The early warning message can be sent to the device used by the target object via SMS or email, etc., so as to facilitate timely handling of abnormal situations in the target version of the service system and ensure the stability of the new version of the service system.

[0071] For example, if the verification result fails, the event alarm device can complete SMS alarm and email alarm to notify the operation and maintenance personnel to handle the fault event.

[0072] Optionally, forwarding the transaction request to a target server in the server cluster based on the target routing rule includes: parsing the target routing rule based on a data format of the target routing rule to obtain a forwarding address of the transaction request; and forwarding the transaction request to the target server based on the forwarding address of the transaction request.

[0073] In this embodiment, the target routing rules can be parsed into a language that can be processed by a computer device (or server), and the destination service cluster address (i.e., forwarding address) in the parsing result can be identified to obtain the destination service cluster address, forward the transaction request to the target server, and process the transaction request, thereby achieving the purpose of accessing business services according to routing rules and ensuring that the expected number of customers use the new version of the business service system.

[0074] Optionally, when the verification result indicates that there is no abnormality in the target version of the service system, after entering the next release stage, it also includes: obtaining the release strategy of the target version of the service system in the next release stage, wherein the release strategy includes at least: in the next release stage, the number of servers for deploying the target version of the service system in the server cluster; based on the release strategy, deploying the target version of the service system in the server cluster.

[0075] In this embodiment, if the verification result indicates that the target version of the service system is not abnormal, after entering the next release phase, the release strategy for the target version of the service system for the next release phase can be obtained. This release strategy may include a grayscale strategy and a transaction routing strategy. The grayscale strategy may include the number of servers in the server cluster to deploy the target version of the service system in the next release phase, and the transaction routing strategy may include routing rules for the next release phase. Based on the release strategy, the deployment scope of the target version of the service system in the server cluster can be expanded, and transaction requests generated in the next release phase can be forwarded according to the transaction routing strategy.

[0076] For example, you can obtain the next phase of business service grayscale strategy. Based on the business service verification results and the next level of business service grayscale strategy, you can generate the next phase of transaction routing strategy, and you can also update the release strategy in real time.

[0077] In this embodiment, routing rules can be customized according to business elements to enable business requests (or transaction requests) to access business services according to specified routes, ensuring that the expected number of customers use the new version of the business service (that is, the service in the target version of the service system), and gradually expand the deployment scope of the new version of the service and the scope of pilot users through intelligent adjustment, and finally complete the launch of the new version of the business service.

[0078] In this embodiment, it is possible to support customized rules for accessing the new version of the service customer group according to the service channels, securities companies, service types and customer numbers configured for the business, and support the hot loading mode of the customer group rules. After automatically identifying that the processing result of the new version of the service has passed the verification, the grayscale range adjustment of the new version of the business service and the rolling upgrade of the server installation can be carried out according to the preset intelligent strategy (for example, after entering the next release stage, the release strategy is adjusted), and finally all servers are updated. Service. When it is identified that the new version of the service has failed the verification, the routing rules for accessing the new version of the service customer group are automatically adjusted to the routing rules of the old version of the service (that is, fall back to the specified release stage), reducing the scope and time of the failure impact and quickly restoring the service.

[0079] By leveraging the advantages of dynamic loading technology for transaction routing rules and automated verification of new business service results, the pilot scope of the new version of the service (for example, the service in the target version of the service system) is intelligently adjusted to ensure that during the launch of the new business service, the pilot scope of the new business service in the next release phase and the installation scope of the server cluster for the new business service can be dynamically adjusted according to the phased verification results, effectively controlling the impact scope when a failure occurs, reducing the impact of the new business service launch on customers, and solving the problem of providing continuous and stable services to customers during the release of new business services.

[0080] Example 2

[0081] The second embodiment of the present invention provides an optional publishing system for a financial service system, which can be used to execute the publishing method for the financial service system provided in the first embodiment of the present invention.

[0082] Figure 2 FIG. 1 is a structural diagram of a publishing system of an optional financial service system according to an embodiment of the present invention. Figure 2As shown, it includes a data collection device 1, a transaction routing rule configuration device 2, a routing rule loading device 3, a business service result verification device 4, a transaction routing strategy update device 5, a service version rolling update strategy device 6, a result notification device 7, and an event alarm device 8. The devices cooperate with each other to jointly realize the grayscale release of the new version of the business service and the rolling installation version of the server.

[0083] Data acquisition device 1: Figure 3 Schematic diagram of the internal structure of an optional data acquisition device 1 according to an embodiment of the present invention. Figure 3 As shown, it includes a bank-securities business request data collection unit 11, which is used to realize real-time collection of bank-securities business request (corresponding to transaction request) data.

[0084] Transaction routing rule configuration device 2: Figure 4 FIG. 1 is a schematic diagram of an optional transaction routing rule configuration device 2 according to an embodiment of the present invention. Figure 4 As shown, it includes: a routing rule configuration unit 21, which is responsible for storing the grayscale release routing rules set by the user; a routing rule parsing unit 22, which completes the grayscale release routing rule parsing and identifies the routing forwarding destination service cluster address; and a routing request forwarding unit 23, which obtains the destination service cluster address and forwards the request.

[0085] Routing rule loading device 3: Figure 5 FIG. 1 is a schematic diagram of the internal structure of an optional routing rule loading device 3 according to an embodiment of the present invention. Figure 5 As shown, it includes: a routing rule change detection unit 31, which is responsible for real-time detection of whether there are new routing rules to be implemented and converting the routing policies to be implemented. A routing rule dynamic loading unit 32 is responsible for loading the routing rules that have not been loaded and have been implemented so that subsequent service requests are forwarded according to the new routing rules.

[0086] Business service result verification device 4: Figure 6 FIG. 4 is a schematic diagram of the internal structure of an optional business service result verification device 4 according to an embodiment of the present invention. Figure 6 As shown, it includes: a business service result verification rule parsing unit 41, which is used to parse the verification rules and obtain the corresponding automated verification script. A verification rule execution unit 42 is used to execute the automated verification script (corresponding to the preset verification script) and store the verification results. A business service grayscale policy update unit 43 is used to perform the following processing according to the results of the automated verification script:

[0087] Result 1: The verification script result (corresponding to the processing result) is consistent with expectations, indicating that there are no abnormalities in the new version of the business service. The next phase of business service expansion grayscale strategy is obtained according to the business service grayscale strategy.

[0088] Result 2: The verification script result is inconsistent with expectations, indicating that the new version of the business service has a fault. Obtain the business service rollback grayscale strategy according to the business service grayscale strategy.

[0089] Transaction routing strategy updating device 5: Figure 7 FIG. 5 is a schematic diagram of the internal structure of an optional transaction routing strategy updating device 5 according to an embodiment of the present invention. Figure 7 As shown, the system includes: a business service result scanning unit 51, which can be used to obtain the business service verification result; a business service grayscale policy scanning unit 52, which can be used to obtain the next-stage business service grayscale policy; and a transaction routing policy generation unit 53, which can be used to generate the next-stage transaction routing policy based on the business service verification result and the next-level business service grayscale policy. The business service grayscale policy and transaction routing policy correspond to the release policy in Example 1.

[0090] Service version rolling update policy device 6: Figure 8 FIG. 1 is a schematic diagram of the internal structure of an optional service version rolling update strategy device 6 according to an embodiment of the present invention. Figure 8 As shown, the system includes: a business service grayscale policy change scanning unit 61, which can be used to detect and obtain the latest policy of the business service grayscale policy update unit in real time; a service version rolling update policy generation unit 62, which can be used to generate the update policy for the next stage of service version rolling based on the latest business service grayscale policy; and a service version update policy execution unit 63.

[0091] Result notification device 7: Figure 9 FIG. 1 is a schematic diagram of the internal structure of an optional result notification device 7 according to an embodiment of the present invention. Figure 9 As shown, it includes: a result notification unit 71, which can notify the terminal user according to the latest policy results in the business service result verification device 4, the transaction routing policy update device 5, and the service version rolling update policy device 6.

[0092] Event alarm device 8: Figure 10 FIG. 8 is a schematic diagram of the internal structure of an optional event alarm device 8 according to an embodiment of the present invention. Figure 10 As shown, it includes: a text message alarm unit 81 and an email alarm unit 82, which can be used to complete text message alarms and email alarms through the event alarm device when the business service verification result in the business service result verification device 4 fails to be verified, to notify the operation and maintenance personnel and handle the fault event.

[0093] The above-mentioned data collection device 1, transaction routing rule configuration device 2, routing rule loading device 3, business service result verification device 4, transaction routing strategy update device 5, service version rolling update strategy device 6, result notification device 7, event alarm device 8, each device cooperates with each other to jointly realize the grayscale release of the new version of business service and the server rolling installation version, etc. Through mutual combination, the entire process of automated grayscale release of new business services can be realized. Specifically, the data collection device 1 is relatively independent and can collect real-time data of banking and securities business requests. It uses the transaction routing rule configuration device 2 to find the routing rules that match the current data request and forward the data request to the service cluster for business service processing. The business service result verification device 4 can verify the new service business results. If the verification passes, the next stage business service grayscale strategy can be generated. If the verification fails, a business service fallback grayscale strategy can be generated. The transaction routing strategy update device 5 and the service version rolling update strategy device 6 can generate the next stage transaction routing strategy and service version rolling update strategy based on the next stage business service grayscale strategy. The routing rule loading device 3 can dynamically load the next stage routing strategy, and the new routing strategy takes effect. The result notification device 7 can be responsible for persisting the latest strategy results in the business service result verification device 4, the transaction routing strategy update device 5, and the service version rolling update strategy device 6. The event alarm device 8 can be responsible for passing the business service verification results in the business service result verification device 4 to the operation and maintenance personnel.

[0094] By leveraging the advantages of dynamic loading technology for transaction routing rules and automated verification of new business service results, the pilot scope of the new version of the service (for example, the service in the target version of the service system) is intelligently adjusted to ensure that during the launch of the new business service, the pilot scope of the new business service in the next release phase and the installation scope of the server cluster for the new business service can be dynamically adjusted based on the phased verification results, effectively controlling the impact scope when a failure occurs, reducing the impact of the new business service launch on customers, and solving the problem of providing continuous and stable services to customers during the release of new business services.

[0095] Example 3

[0096] The third embodiment of the present invention provides an optional publishing device of a financial service system, wherein each implementation unit in the publishing device corresponds to each implementation step in the first embodiment.

[0097] Figure 11 is a schematic diagram of an optional publishing device of a financial service system according to an embodiment of the present invention, such as Figure 11 As shown, the publishing device includes: a first processing unit 111, a forwarding unit 112, a verification unit 113 and a second processing unit 114.

[0098] The first processing unit 111 is configured to locate the current release phase during the release of the target version of the service system, receive a transaction request, and search for a routing rule matching the transaction request to obtain a target routing rule. The release of the target version of the service system includes N release phases. In each release phase, the number of servers deploying the target version of the service system in the server cluster is higher than in the previous release phase. The target routing rule is used to determine a forwarding address for the transaction request, where N is a positive integer.

[0099] A forwarding unit 112 is configured to forward the transaction request to a target server in the server cluster based on a target routing rule, wherein the target server is configured to process the transaction request and obtain a processing result of the transaction request;

[0100] A verification unit 113 is configured to verify whether the target version of the service system has an anomaly based on the processing result, and obtain a verification result;

[0101] The second processing unit 114 is configured to, if the verification result indicates that there is no abnormality in the target version of the service system, proceed to the next release phase until N release phases are completed.

[0102] In the publishing device of the financial service system provided in the third embodiment of the present invention, a first processing unit 111 can be used to locate the current publishing stage during the publishing process of the target version of the service system, receive a transaction request, and search for a routing rule matching the transaction request to obtain a target routing rule. The publishing process of the target version of the service system includes N publishing stages. In each publishing stage, the number of servers in the server cluster deploying the target version of the service system is greater than that in the previous publishing stage. The target routing rule is used to determine the forwarding address of the transaction request, where N is a positive integer. The forwarding unit 112 then forwards the transaction request to the target server in the server cluster based on the target routing rule. The target server processes the transaction request and obtains a processing result of the transaction request. The verification unit 113 then verifies whether there is an anomaly in the target version of the service system based on the processing result to obtain a verification result. If the verification result indicates that there is no anomaly in the target version of the service system, the second processing unit 114 proceeds to the next publishing stage, and the process continues until the N publishing stages are completed. This solves the technical problem of poor publishing performance of new versions of business service systems in related technologies.

[0103] In this embodiment, the target version of the service system is gradually deployed to the server cluster through multiple release stages, and in each release stage, the transaction request is forwarded to the corresponding server for processing through pre-defined routing rules. This avoids the situation in related technologies where the new version of the service system is directly deployed to all servers after verification when gray release is adopted, which leads to a wide range of impact after failure. This achieves the technical effect of reducing the impact range of failures and improving the stability of system releases when releasing a new version of the business service system.

[0104] Optionally, in the publishing device of the financial service system provided in Example 3 of the present invention, the verification unit includes: a verification sub-unit, used to obtain a preset verification script, and execute the preset verification script to verify whether the processing result is consistent with the expected result; a first determination sub-unit, used to determine that the verification result indicates that there is no abnormality in the target version of the service system when the processing result is consistent with the expected result; and a second determination sub-unit, used to determine that the verification result indicates that there is an abnormality in the target version of the service system when the processing result is inconsistent with the expected result.

[0105] Optionally, in the publishing device of the financial service system provided in Example 3 of the present invention, the publishing device of the financial service system also includes: a first acquisition unit, used to obtain the parameter data filled in the target page during the publishing process of the target version of the service system, and generate routing rules corresponding to the parameter data, wherein the target page is used to configure the parameters of the routing rules; a storage unit, used to store the routing rules corresponding to the parameter data to the target storage space.

[0106] Optionally, in the publishing device of the financial service system provided in Example 3 of the present invention, the first processing unit includes: a reading sub-unit, used to read the routing rules stored in the target storage space to obtain S routing rules, where S is a positive integer greater than 1; a matching sub-unit, used to match the transaction data carried in the transaction request with the S routing rules, and determine the routing rule that matches the transaction data as the target routing rule.

[0107] Optionally, in the publishing device of the financial service system provided in Example 3 of the present invention, the publishing device of the financial service system also includes: a rollback unit, which is used to roll back to the specified publishing stage and generate early warning information when the verification result indicates that there is an abnormality in the target version of the service system, wherein the early warning information is used to prompt the target object that there is a fault in the target version of the service system in the current publishing stage, and the specified publishing stage includes: the publishing stage before the current publishing stage; and a sending unit, which is used to send the early warning information to the device used by the target object.

[0108] Optionally, in the publishing device of the financial service system provided in Example 3 of the present invention, the forwarding unit includes: a parsing sub-unit, which is used in the publishing device of the financial service system provided in Example 3 of the present invention to parse the target routing rules based on the data format of the target routing rules to obtain the forwarding address of the transaction request; and a forwarding sub-unit, which is used to forward the transaction request to the target server based on the forwarding address of the transaction request.

[0109] Optionally, in the publishing device of the financial service system provided in Example 3 of the present invention, the publishing device of the financial service system also includes: a second acquisition unit, which is used to obtain the publishing strategy of the target version of the service system in the next publishing stage after entering the next publishing stage when the verification result indicates that there is no abnormality in the target version of the service system, wherein the publishing strategy includes at least: the number of servers for deploying the target version of the service system in the server cluster in the next publishing stage; and a deployment unit, which is used to deploy the target version of the service system in the server cluster based on the publishing strategy.

[0110] The publishing device of the above-mentioned financial service system may also include a processor and a memory. The above-mentioned first processing unit 111, forwarding unit 112, verification unit 113 and second processing unit 114 are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0111] The processor includes a kernel that retrieves the corresponding program unit from memory. One or more kernels can be configured, and by adjusting kernel parameters, the target version of the service system is gradually deployed to the server cluster through multiple release phases. At each release phase, transaction requests are forwarded to the corresponding server for processing using predefined routing rules. This avoids the situation in related technologies where a new version of the service system is directly deployed to all servers after verification during a grayscale release, which can have a wide-ranging impact if a failure occurs. This achieves the technical effect of reducing the impact of failures and improving the stability of system releases when releasing new versions of business service systems.

[0112] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0113] According to another aspect of an embodiment of the present invention, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned publishing methods of the financial service system by executing the executable instructions.

[0114] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, which stores a computer program, wherein when the computer program runs, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned methods for publishing a financial service system.

[0115] Figure 12 is a schematic diagram of an electronic device according to an embodiment of the present invention, such as Figure 12 As shown, an embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program stored in the memory and runnable on the processor. When the processor executes the program, any one of the above-mentioned publishing methods of the financial service system is implemented.

[0116] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0117] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0118] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0119] The units described as separate components may or may not be physically separate, and 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 may be selected according to actual needs to achieve the purpose of the present embodiment.

[0120] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0121] If the integrated unit is implemented in the form of 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, 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. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc. Various media that can store program codes.

[0122] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A publishing method for a financial service system, characterized in that: include: During the release of the target version of the service system, the current release stage is located, a transaction request is received, and a routing rule matching the transaction request is searched to obtain a target routing rule. The release of the target version of the service system includes N release stages. In each release stage, the number of servers deploying the target version of the service system in the server cluster is greater than that in the previous release stage. The target routing rule is used to determine a forwarding address for the transaction request, where N is a positive integer greater than 1. forwarding the transaction request to a target server in the server cluster based on the target routing rule, wherein the target server is configured to process the transaction request and obtain a processing result of the transaction request; Based on the processing result, verify whether the service system of the target version has an abnormality, and obtain a verification result; If the verification result indicates that there is no abnormality in the service system of the target version, enter the next release phase until N release phases are completed; When the verification result indicates that an abnormality exists in the service system of the target version, the system rolls back to a designated release stage, wherein the designated release stage includes a release stage before the current release stage.

2. The publishing method of the service system according to claim 1, characterized in that: Based on the processing result, verify whether the service system of the target version has an abnormality, and obtain a verification result, including: Obtain a preset verification script and execute the preset verification script to verify whether the processing result is consistent with the expected result; If the processing result is consistent with the expected result, determining that the verification result indicates that there is no abnormality in the target version of the service system; In a case where the processing result is inconsistent with the expected result, it is determined that the verification result indicates that an abnormality exists in the service system of the target version.

3. The publishing method of the service system according to claim 1, characterized in that: The process of publishing the target version of the service system also includes: Obtain parameter data filled in the target page and generate routing rules corresponding to the parameter data, wherein the target page is used to configure the parameters of the routing rules; The routing rules corresponding to the parameter data are stored in the target storage space.

4. The publishing method of the service system according to claim 3, characterized in that: Find the routing rule that matches the transaction request and obtain the target routing rule, including: Reading the routing rules stored in the target storage space to obtain S routing rules, where S is a positive integer greater than 1; The transaction data carried in the transaction request is matched with the S routing rules, and the routing rule that matches the transaction data is determined as the target routing rule.

5. The publishing method of the service system according to claim 1, characterized in that: If the verification result indicates that the service system of the target version has an abnormality, generating an early warning message, wherein the early warning message is used to prompt the target object that the service system of the target version has a fault in the current release stage; The warning information is sent to the device used by the target object.

6. The publishing method of the service system according to claim 1, characterized in that: Forwarding the transaction request to a target server in the server cluster based on the target routing rule includes: parsing the target routing rule based on a data format of the target routing rule to obtain a forwarding address for the transaction request; The transaction request is forwarded to the target server based on the forwarding address of the transaction request.

7. The publishing method of the service system according to claim 1, characterized in that: If the verification result indicates that there is no abnormality in the target version of the service system, after entering the next release phase, the method further includes: Obtaining a release strategy for the target version of the service system in the next release phase, wherein the release strategy at least includes: the number of servers in the server cluster deploying the target version of the service system in the next release phase; Based on the release strategy, the service system of the target version is deployed in the server cluster.

8. A publishing device for a financial service system, characterized in that: include: a first processing unit configured to, during a release process of a target version of the service system, locate a current release phase, receive a transaction request, and search for a routing rule matching the transaction request to obtain a target routing rule, wherein the release process of the target version of the service system includes N release phases, and in each release phase, the number of servers deploying the target version of the service system in a server cluster is greater than that in a previous release phase. The target routing rule is used to determine a forwarding address for the transaction request, where N is a positive integer greater than 1; a forwarding unit, configured to forward the transaction request to a target server in the server cluster based on the target routing rule, wherein the target server is configured to process the transaction request and obtain a processing result of the transaction request; A verification unit, configured to verify whether the target version of the service system has an abnormality based on the processing result, and obtain a verification result; A second processing unit is configured to, if the verification result indicates that there is no abnormality in the service system of the target version, enter the next release stage until N release stages are completed; When the verification result indicates that an abnormality exists in the service system of the target version, the system rolls back to a designated release stage, wherein the designated release stage includes a release stage before the current release stage.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located is controlled to execute the publishing method of the financial service system according to any one of claims 1 to 7.

10. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the publishing method of the financial service system described in any one of claims 1 to 7.

Images