Business processing method and device based on distributed financial system, and storage medium

Abstract

The embodiment of the invention provides a business processing method and device based on a distributed financial system and a storage medium. The method is applied to the distributed financial system, the system comprises an orchestration service and a plurality of micro-services, each micro-service comprises a plurality of sub-transaction components, and the method comprises the steps of determining a plurality of target sub-transaction components corresponding to a transaction request based on the orchestration service in response to the transaction request; processing the transaction request by progressively calling the target sub-transaction component based on the arrangement service and a target micro-service corresponding to the target sub-transaction component to obtain a processing result of the target transaction request; wherein the progressive call characterization orchestration service calls a target sub-transaction component of a target micro-service, the target sub-transaction component calls a target unit component, and the target unit component calls a target function component. According to the method, the transaction processing efficiency can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of financial technology, and in particular to a business processing method and device based on a distributed financial system and a storage medium. BACKGROUND

[0002] In daily life, operations such as transfer, deposit and loan cannot be carried out without the processing of transaction data by a financial system.

[0003] In related technologies, a financial system usually integrates multiple business functions and is deployed in a server. However, with the rapid growth of transaction data, the centralized financial system has low efficiency in transaction processing and cannot meet current business requirements. SUMMARY

[0004] The embodiments of the present application provide a business processing method and device based on a distributed financial system and a storage medium, so as to improve the efficiency of transaction processing.

[0005] In a first aspect, the embodiments of the present application provide a business processing method based on a distributed financial system. The method is applied to a distributed financial system, and the system includes an orchestration service and multiple microservices. Each microservice includes multiple sub-transaction components, and the method includes:

[0006] Based on the orchestration service, a plurality of target sub-transaction components corresponding to a transaction request are determined in response to the transaction request.

[0007] Based on the orchestration service and a target microservice corresponding to the target sub-transaction component, the target sub-transaction component is called in a progressive manner to process the transaction request, and a processing result of the target transaction request is obtained. The progressive calling represents that the orchestration service calls the target sub-transaction component of the target microservice, the target sub-transaction component calls a target unit component, and the target unit component calls a target function component.

[0008] In a possible implementation, the method of determining the plurality of target sub-transaction components corresponding to the transaction request based on the orchestration service in response to the transaction request includes:

[0009] Based on the orchestration service, a target orchestration microservice corresponding to the transaction request is determined in response to the transaction request.

[0010] Based on the target orchestration microservice, a target orchestration rule of the transaction request is determined. The target orchestration rule represents the target sub-transaction component required by the transaction request and the calling logic between the target sub-transaction components.

[0011] Based on the target orchestration microservice and the target orchestration rule, the target sub-transaction component is determined.

[0012] In a possible implementation, the determining the target sub-transaction component based on the target orchestration microservice and the target orchestration rule comprises:

[0013] The target orchestration microservice is used to sequentially perform entry condition verification on each sub-transaction component included in the target orchestration rule, and if it is determined that the sub-transaction component meets a preset sub-transaction entry condition, the sub-transaction component is determined as the target sub-transaction component corresponding to the transaction request.

[0014] In a possible implementation, the orchestration service includes a target orchestration microservice corresponding to the transaction request, and the processing the transaction request by progressively invoking the target sub-transaction component based on the orchestration service and a target microservice corresponding to the target sub-transaction component to obtain a processing result of the target transaction request comprises:

[0015] The target orchestration microservice is used to remotely invoke a target sub-transaction component of the target microservice to process the transaction request, and obtain an output result of the target sub-transaction component.

[0016] In the process of processing the transaction request by the target sub-transaction component, the target microservice is used to locally invoke a target unit component to process the transaction request; and in the process of processing the transaction request by the target unit component, the target microservice is used to locally invoke a target function component to process the transaction request.

[0017] The target orchestration microservice is used to determine the processing result according to the output result of the target sub-transaction component.

[0018] In a possible implementation, the orchestration service includes a target orchestration microservice corresponding to the transaction request, and the method further comprises:

[0019] In the process of processing the transaction request by the target sub-transaction component, if it is determined according to a preset processing logic that a message needs to be sent, event information is determined.

[0020] The target microservice is used to generate a task identifier and task information of an event task according to the event information.

[0021] The target microservice is used to store the task identifier into a first database table and write the task information into a second database table.

[0022] In a possible implementation, the system further comprises a proxy service, and the method further comprises:

[0023] If it is determined according to the processing result that a message needs to be sent, based on the proxy service, a task identifier stored in the first database table is stored into an event submission queue;

[0024] Based on the proxy service, a first task identifier in the event submission queue is extracted, and according to the task identifier, task information of an event task corresponding to the task identifier is determined;

[0025] Based on the proxy service, a message is generated and pushed according to the task identifier and the task information.

[0026] In a possible implementation, the generating and pushing of the message according to the task identifier and the task information based on the proxy service includes:

[0027] A task processor is allocated for the event task according to the task identifier and the task information;

[0028] Based on the proxy service, the event task is processed according to the allocated task processor, and the message is generated and pushed.

[0029] In a possible implementation, before the plurality of target sub-transaction components corresponding to the transaction request are determined, the method further includes:

[0030] Based on the orchestration service, a current accounting time is obtained in response to the transaction request;

[0031] Based on the orchestration service, a remainder value is obtained by performing a remainder operation on the current accounting time;

[0032] According to the remainder value, a key value corresponding to the remainder value is determined;

[0033] A preset value corresponding to the key value is incremented by one, and the incremented value is used as a transaction serial number of the transaction request.

[0034] In a possible implementation, after the key value corresponding to the remainder value is determined, the method further includes:

[0035] Based on the orchestration service, if it is determined that the type of the transaction request is daily cut batch processing, the current accounting time is updated;

[0036] Based on the orchestration service, a remainder value is obtained by performing a remainder operation on the updated current accounting time;

[0037] A preset value corresponding to the key value corresponding to the updated remainder value is set to zero.

[0038] In a second aspect, the embodiments of the present application provide a business processing apparatus based on a distributed financial system. The apparatus is applied to a distributed financial system, and the system includes an orchestration service and a plurality of microservices. Each microservice includes a plurality of sub-transaction components, including:

[0039] A determination module is configured to determine, based on the orchestration service, a plurality of target sub-transaction components corresponding to a transaction request in response to the transaction request.

[0040] A processing module is configured to process the transaction request by progressively invoking the target sub-transaction components based on the orchestration service and target microservices corresponding to the target sub-transaction components, to obtain a processing result of the target transaction request. The progressive invocation represents that the orchestration service invokes the target sub-transaction components of the target microservices, the target sub-transaction components invoke target unit components, and the target unit components invoke target function components.

[0041] In a third aspect, the embodiments of the present application provide an electronic device, including a memory and a processor.

[0042] The memory stores computer execution instructions.

[0043] The processor executes the computer execution instructions stored in the memory, so that the processor executes the first aspect and / or various possible implementation manners of the first aspect.

[0044] In a fourth aspect, the embodiments of the present application provide a computer readable storage medium, which stores computer execution instructions. The computer execution instructions are executed by a processor to implement the first aspect and / or various possible implementation manners of the first aspect.

[0045] In a fifth aspect, the embodiments of the present application provide a computer program product, which includes a computer program. The computer program is executed by a processor to implement the first aspect and / or various possible implementation manners of the first aspect.

[0046] The business processing method and device based on the distributed financial system and the storage medium provided by the embodiment of the application, the distributed financial system can determine the target sub-transaction component corresponding to the transaction request based on the arrangement service, realize the splitting and decoupling of the transaction request, and route the transaction request to the target micro service corresponding to the target sub-transaction component in the process of calling the target sub-transaction component to process the transaction request, process the transaction request based on the target micro service calling the target sub-transaction component, further call the target unit component for processing in the process of the target sub-transaction component processing, further call the target function component for processing in the process of the target unit component processing, realize the multi-level decoupling of the micro service, and obtain the processing result of the transaction request. In this way, the transaction request can be dispersed to multiple micro services for processing, the efficiency of transaction processing is improved, and through the multi-level decoupling of the micro service, the progressive calling based on the sub-transaction component, the unit component and the function component can fully utilize the parallel processing capability of the micro service architecture, and further improve the transaction processing efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0047] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0048] Figure 1 A structure schematic diagram of a distributed financial system provided by the application;

[0049] Figure 2 A micro service level division schematic diagram provided by the application;

[0050] Figure 3 A flowchart of a business processing method based on a distributed financial system provided by the application Figure 1 ;

[0051] Figure 4 A flowchart of a business processing method based on a distributed financial system provided by the application Figure 2 ;

[0052] Figure 5 A schematic diagram of an application scenario provided by the application;

[0053] Figure 6 A schematic diagram of another application scenario provided by the application;

[0054] Figure 7 A schematic diagram of still another application scenario provided by the application;

[0055] Figure 8 A flowchart of a business processing method of a distributed financial system provided by the application Figure 3 ;

[0056] Figure 9 A structural schematic diagram of a business processing apparatus based on a distributed financial system is provided for the present application;

[0057] Figure 10 A structural schematic diagram of an electronic device is provided for the present application.

[0058] The specific embodiments of the present application have been shown by the above-described drawings, and will be described in more detail hereinafter. These drawings and written descriptions are not intended to limit the scope of the concept of the present application by any means, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0059] The exemplary embodiments will be described in detail herein with reference to the accompanying drawings. In the following description, the same numbers refer to the same or similar elements unless otherwise represented. The embodiments described in the following exemplary embodiments do not represent all the embodiments consistent with the present application. Rather, they are merely examples of devices and methods consistent with some aspects of the present application, as detailed in the appended claims.

[0060] The financial system with centralized business functions has low processing efficiency for high burst and large data volume transaction requests. Therefore, the business processing method based on a distributed financial system provided by the present application abstracts and parameterizes each original transaction of the financial system on the basis of a micro-service architecture, splits the original transaction into a plurality of sub-transaction components corresponding to the original transaction, and realizes the processing of the original transaction by scheduling the sub-transaction components. Meanwhile, the business functions corresponding to the micro-services are split and decoupled in multiple levels, and the sub-transaction components are called based on the multi-level and atomic components. In this way, in the case of high burst and large data volume, transaction requests can be dispersed to multiple micro-services for processing, improving the efficiency of transaction processing. Moreover, by decoupling the business functions of the micro-services, the multi-level and atomic components can fully utilize the parallel processing capability of the micro-service architecture, further improving the efficiency of transaction processing.

[0061] Figure 1 A structural schematic diagram of a distributed financial system is provided for the present application, as shown in Figure 1 The distributed financial system includes deposit centers, loan centers, pricing centers, and other real-time transaction centers (hereinafter referred to as transaction centers), as well as parameter centers, subscription and push centers, accounting centers, log centers, and monitoring centers. The transaction centers are split and decoupled based on business functions to obtain scheduling services and a plurality of micro-services. Figure 1 is shown by including 2 micro-services.

[0062] Microservice is a loosely-coupled and autonomous service after the application corresponding to a business function is split. Each service can be developed, deployed and expanded independently, in other words, microservice can be used to implement part of the business function. It should be noted that the embodiments of the present application do not limit the deployment mode of microservice, for example, each microservice can be deployed in a server cluster, or multiple microservices can be deployed in a server cluster. Table 1 is a schematic diagram of microservices included in the distributed financial system provided by the embodiments of the present application, and a function schematic diagram of each microservice.

[0063] Optionally, the microservice can be further classified, referring to the microservices shown in Table 1, which can be divided into business microservices and basic microservices. Among them, the business microservice represents that it can be run independently to implement the corresponding business function, for example, it can include the private deposit service, the corporate deposit service and the internal account service shown in Table 1. The basic microservice represents that it needs to be combined with other basic microservices or business microservices to run to implement the corresponding business function, for example, it can include the pricing service, the customer service, the operation service, the aggregation service, the account processing service, the registration service, the file processing service and the message processing service shown in Table 1.

[0064] Table 1: Microservice and its function

[0065]

[0066] In the embodiments of the present application, each microservice is further hierarchically split based on the business function, referring to Figure 2 Figure 2 is a schematic diagram of microservice hierarchy provided by the present application, each microservice can be logically divided into three layers: sub-transaction component, unit component and function component.

[0067] The sub-transaction component is used to complete the overall scheduling of the business, and does not implement the business function itself, but implements the business function by calling the unit component, in other words, the sub-transaction component can be regarded as a main scheduling program. It should be noted that in the embodiments of the present application, the sub-transaction component can allow cross-service calling of the unit component of other microservices, in other words, the sub-transaction component of microservice 1 can call the unit component of microservice 2.

[0068] The unit component is the smallest business unit of the bank business, which is used to complete part of the function of the sub-transaction, and the distributed financial system mainly implements the control of the business integrity through the unit component. For the unit component, the business function is mainly implemented by calling the function component. It should be noted that in the embodiments of the present application, the unit component does not allow cross-service calling of the function component of other microservices, and does not allow calling the sub-transaction component.

[0069] ​The function component encapsulates functions such as resource access, logical judgment, and calculation, and provides the function component for use by the upper unit component. It should be noted that in the embodiments of the present application, the function component is not allowed to call the function component of other microservices, is not allowed to call the sub-transaction component, and is not allowed to call the unit component.

[0070] It should be noted that the functions of the components at each layer do not overlap, and the layers are decoupled to avoid functional redundancy and coupling. Meanwhile, the upper layer component can access the interface of the lower layer component, but the lower layer component does not depend on the logic of the upper layer component.

[0071] By layering the microservices, the complex transaction processing logic can be decoupled, the layers are kept in a loosely coupled relationship, the detailed processing logic inside each layer is encapsulated, the influence of the current layer on adjacent layers is shielded, and services are provided for adjacent layers to simplify the processing of other layers, improve efficiency and reusability, make the entire system easier to expand, and the expansion process is performed in a pre-designed mechanism, without impacting the entire system architecture, maintaining the core running stability, quickly responding to business needs, and supporting continuous business development.

[0072] The orchestration service is used to orchestrate the sub-transaction components provided by the microservices to form the interface of the original transaction. The orchestration service can also be used for global transaction control, global exception handling, and the like. The original transaction represents the original transaction processing logic that has not been split.

[0073] In some possible implementation manners, based on all original transactions required to be processed by the transaction center, the original transactions are classified to obtain a plurality of orchestration microservices, and the hardware resources and software resources required by each orchestration microservice are different. Table 2 shows the orchestration microservices included in the orchestration service according to an embodiment of the present application, and the original transactions included in each orchestration microservice.

[0074] Table 2: Orchestration microservices and original transactions included therein

[0075]

[0076] In this implementation manner, each orchestration microservice can include a plurality of original transactions, wherein the transaction execution flow of the original transaction is abstracted and parameterized and then packaged, and each original transaction is completely decoupled. A corresponding orchestration rule is set for each original transaction, and then the received transaction request can be attributed to the corresponding original transaction, and the original transaction is split and decoupled based on the orchestration rule of the original transaction to obtain the sub-transaction component, and then the orchestration processing of the sub-transaction component is implemented. Table 3 shows the content of an orchestration rule according to an embodiment of the present application.

[0077] Table 3: Orchestration rule

[0078]

[0079] Through the definition of the original transaction above, the distributed financial system can arbitrarily extend the required original transaction, improving the scalability of the system, and the extended original transaction will not affect the existing original transaction.

[0080] In this implementation, the original transaction can include one or more sub-transaction components after orchestration. The orchestration microservice can be based on remote calls to the sub-transaction component, such as a Representational State Transfer (RESTful) interface based on Hypertext Transfer Protocol (HTTP), or a Remote Procedure Call (RPC) protocol based on Transmission Control Protocol (TCP). A sub-transaction component can include one or more unit components under the microservice. The sub-transaction component can be based on local calls to the unit component, i.e., the unit component is locally dependent on the sub-transaction component. In other words, the sub-transaction component and the unit component run in the same microservice, and their communication and interaction is achieved through local method calls or object references. A unit component can include one or more function components under the microservice. The unit component calls the function component in a local manner, i.e., the function component is locally dependent on the unit component.

[0081] In some possible implementations, the distributed financial system can also include a public component representing general processing logic of business functions, which can be called by any of the aforementioned types of components to implement business functions. The public component may, for example, include: an authority management component, an account management component, an event registration component, a password management component, a parameter management component, a thread management component, etc., which are not limited by the embodiments of the present application.

[0082] In some possible implementations, the distributed financial system can also include a channel integration service responsible for coordinating communication between different services, protocols or networks. For example, the channel integration service can implement the following functions:

[0083] (1) Protocol conversion: used to convert transaction requests into the request format preset by the distributed financial system, such as converting HTTP requests into gRPC or WebSocket requests.

[0084] (2) Load balancing and routing: used to route transaction requests to orchestration services, or distribute transaction requests using algorithms such as round robin, weighted round robin, etc.

[0085] (3) Flow control and throttling: used to set the maximum number of requests per second, or return a default response when the service is unavailable.

[0086] (4) Logging and monitoring: used to generate global link trace numbers, record request times, response status codes, delays, and other information.

[0087] (5) Request and response transformation: used to modify the content of requests or responses, such as adding, deleting, or modifying header information.

[0088] (6) Security control: used for permission authentication of request channels and transactions, or encryption of request data.

[0089] Specifically, the distributed financial system can receive transaction requests from various channels based on channel integration services, process the transaction requests, and route them to orchestration services.

[0090] The technical solutions of the present application and how the technical solutions of the present application solve the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0091] Figure 3 Flowchart of the business processing method based on the distributed financial system provided by the present application Figure 1 As shown in Figure 3 , the method comprises:

[0092] S101, based on the orchestration service, in response to the transaction request, determine the multiple target sub-transaction components corresponding to the transaction request.

[0093] Exemplarily, the above transaction request represents a to-be-processed original transaction, which can come from a client or a teller system. Optionally, the transaction request can be preprocessed based on the channel integration service before entering the orchestration service. The target sub-transaction component represents the sub-transaction component corresponding to the original transaction indicated by the transaction request.

[0094] In one example, as mentioned above, the distributed financial system splits the original transaction into multiple sub-transaction components, so the distributed financial system can determine the original transaction corresponding to the transaction request based on the orchestration service, and further determine the sub-transaction components corresponding to the original transaction as the multiple target sub-transaction components corresponding to the transaction request.

[0095] For example, a transaction request may carry a transaction identifier, and the orchestration service may preset a correspondence between the transaction identifier and the original transaction, as well as the sub-transaction component corresponding to the original transaction. Thus, the distributed financial system may determine the corresponding original transaction based on the transaction request, and further determine multiple target sub-transaction components corresponding to the transaction request.

[0096] S102 : Based on the orchestration service and the target microservice corresponding to the target sub-transaction component, the transaction request is processed by progressively calling the target sub-transaction component to obtain a processing result of the target transaction request.

[0097] For example, as mentioned above, each microservice in a distributed financial system includes multiple sub-transaction components, multiple unit components, and multiple function components. The target microservice represents the microservice corresponding to the target sub-transaction component; the target unit component represents the unit component required by the target sub-transaction component; and the target function component represents the function component required by the target unit component. The progressive call represents the orchestration service calling the target sub-transaction component of the target microservice, the target sub-transaction component calling the target unit component, and the target unit component calling the target function component. It should be noted that when designing microservices at multiple levels, the correspondence between sub-transaction components and unit components, as well as the correspondence between unit components and function components, is preset.

[0098] In one example, a distributed financial system can first orchestrate each target sub-transaction component based on an orchestration service to obtain an orchestrated target sub-transaction component. Then, for each target sub-transaction component, the orchestration service can call the target sub-transaction component by remotely accessing the target microservice corresponding to the target sub-transaction component, thereby processing the transaction request based on the target sub-transaction component. Finally, the processing result of the transaction request can be determined based on the orchestration service. In the process of remotely accessing the target microservice corresponding to the target sub-transaction component, the distributed financial system can route the transaction request to the target microservice and, based on the target microservice, locally call the target sub-transaction component to process the transaction request. In the process of the target sub-transaction component processing the transaction request, the target sub-transaction component will further decompose the transaction request and can locally call the target unit component to process the transaction request. In the process of the target unit component processing the transaction request, the target unit component can locally call the target function component to process the transaction request.

[0099] Optionally, the distributed financial system can generate a response message to the transaction request based on the orchestration service and the processing results. This response message represents the distributed financial system's response to the transaction request and may include information such as the transaction status, transaction results, and transaction details (e.g., transaction amount, transaction time, etc.), which is not limited in this embodiment of the present application.

[0100] The embodiment of the present application provides a business processing method based on a distributed financial system. The distributed financial system can determine the target sub-transaction component corresponding to the transaction request based on the orchestration service, realize the splitting and decoupling of the transaction request, and in the process of calling the target sub-transaction component to process the transaction request, route the transaction request to the target microservice corresponding to the target sub-transaction component, call the target sub-transaction component based on the target microservice to process the transaction request, and in the process of processing the target sub-transaction component, further call the target unit component for processing, and in the process of processing the target unit component, further call the target function component for processing, realize multi-level decoupling of microservices, and obtain the processing result of the transaction request. In this way, the transaction request can be dispersed to multiple microservices for processing, thereby improving the efficiency of transaction processing. Moreover, through the multi-level decoupling of microservices, based on the progressive calling of sub-transaction components, unit components, and function components, the parallel processing capability of the microservice architecture can be fully utilized, further improving the efficiency of transaction processing.

[0101] Figure 4 Schematic diagram of the business processing method based on the distributed financial system provided in this application Figure 2 , Figure 5 A schematic diagram of an application scenario provided by this application, combined with Figure 4 and Figure 5 As shown, this embodiment Figure 3 Based on the embodiment, a business processing method based on a distributed financial system is described in detail. The method includes:

[0102] S201 : Based on the orchestration service, in response to a transaction request, determine a target orchestration microservice corresponding to the transaction request.

[0103] For example, as mentioned above, the original transactions can be classified and assigned to the orchestration microservice, which can provide orchestration services for the original transactions included. The distributed financial system can determine the original transaction corresponding to the transaction request based on the transaction identifier carried in the transaction request based on the orchestration service, and then determine the target orchestration microservice corresponding to the transaction request based on the corresponding relationship between the original transaction and the orchestration microservice. For example, refer to Figure 5 As shown, the orchestration service includes orchestration microservice 1 and orchestration microservice 2. According to the transaction identifier of the transaction request, it can be determined that the target orchestration microservice corresponding to the transaction request is orchestration microservice 1.

[0104] S202: Determine a target orchestration rule for the transaction request based on the target orchestration microservice.

[0105] For example, the target orchestration microservice can provide orchestration services for the included original transactions, including orchestration rules for each original transaction. These orchestration rules are used to indicate the sub-transaction components required by the original transaction and the call logic between the sub-transaction components. These target orchestration rules represent the target sub-transaction components required by the transaction request and the call logic between the target sub-transaction components.

[0106] In one example, the target orchestration microservice presets the correspondence between the original transaction and the orchestration rules. The orchestration rules can be shown in Table 3. The target orchestration microservice presets the calling logic of the sub-transaction components for the original transaction. Then, the distributed financial system can determine the target orchestration rules based on the target orchestration microservice and the correspondence between the transaction request, the original transaction, and the orchestration rules.

[0107] S203: Determine the target sub-transaction component based on the target orchestration microservice and the target orchestration rule.

[0108] In some possible implementations, the orchestration rule indicates the required sub-transaction component. After determining the target orchestration rule, the target sub-transaction component can be determined. It is understood that this step involves determining the identifier of the target sub-transaction component, such as the sub-transaction component's name or identification number (ID).

[0109] In some possible implementations, the orchestration rule specifies the required sub-transaction components, but entry conditions need to be verified for each sub-transaction component to accurately determine the target sub-transaction component. For example, based on the target orchestration microservice, entry conditions are verified for each sub-transaction component included in the target orchestration rule. If a sub-transaction component is determined to meet the pre-set sub-transaction entry conditions, the sub-transaction component is determined to be the target sub-transaction component corresponding to the transaction request.

[0110] Specifically, taking the target sub-transaction components corresponding to the transaction request as sub-transaction component 1 and sub-transaction component 3 as an example, refer to Figure 6 As shown, Figure 6 This is a schematic diagram of another application scenario provided by this application. As shown in Table 3, after the original transaction is abstracted and parameterized, entry conditions can be set for each sub-transaction component. After determining the target orchestration rules, the distributed financial system can sequentially determine, based on the transaction request, whether the transaction information carried in the transaction request meets the entry conditions of the sub-transaction component. If so, the sub-transaction component is determined as the target sub-transaction component. If not, the entry conditions of the next sub-transaction component are verified.

[0111] Optional, reference Figure 6As shown, the received transaction request can be subjected to rule checking and pre-processing of request parameters based on the orchestration service, wherein the rule checking may, for example, include non-empty checking, length checking, format checking, etc. of the request parameters; the pre-processing may, for example, include transaction state checking, system accounting time acquisition, agency clerk checking, system control information checking, transaction serial number generation, etc. A context object can also be created based on the orchestration service, which is used to store and manage data structures of data and information related to the current process. The context object may, for example, include transaction identification and transaction information carried in the transaction request, and output results of each sub-transaction component, etc. It can be understood that each sub-transaction component can process the transaction request based on the incoming context object.

[0112] S204, based on the target orchestration microservice, remotely calling the target sub-transaction component of the target microservice to process the transaction request and obtain the output result of the target sub-transaction component.

[0113] In the process of processing the transaction request by the target sub-transaction component, the target microservice is used to process the transaction request by locally calling the target unit component; in the process of processing the transaction request by the target unit component, the target microservice is used to process the transaction request by locally calling the target function component.

[0114] For example, referring to Figure 6 As shown, after the distributed financial system determines the target sub-transaction component based on the target orchestration service, the target sub-transaction component can be scheduled and remotely called to process the transaction request and return the output result of the target sub-transaction component; wherein the target sub-transaction component can be remotely called by routing the transaction request to the target microservice corresponding to the target sub-transaction component for processing, and then the target unit component required by the target sub-transaction component can be locally called based on the target microservice to process the transaction request; in the process of processing the target unit component, the target function component is locally called based on the target microservice to process the transaction request, and finally the output result of the target sub-transaction component is obtained.

[0115] Specifically, referring to Figure 5 As shown, in the process of remotely calling the sub-transaction component 1, the transaction request is routed to the microservice 1, and then the sub-transaction component 1 is called based on the microservice 1 to process the transaction request; in the process of processing the sub-transaction component 1, the unit component 1-3 is locally called based on the microservice 1 to process the transaction request; in the process of processing the unit component 1, the function component 1 is locally called for processing, and in the process of processing the unit component 2, the function component 2 is locally called for processing, and finally the output result of the sub-transaction component 1 is obtained and returned to the target orchestration microservice (orchestration microservice 1).Figure 6 As shown, after the sub-transaction component 1 is invoked by the microservice 1 to process the transaction request, the output result of the sub-transaction component is returned to the orchestration microservice, and the output result of the sub-transaction component is input to other sub-transaction components based on the preset orchestration rule, or the output result of each sub-transaction component is used to make a decision on the processing result of the transaction request, or the output result of each sub-transaction component is stored in a context object for invocation of other sub-transaction components. The invocation process of the sub-transaction component 3 is similar, and details are not described herein.

[0116] It should be noted that the scheduling logic of the sub-transaction component is not limited in the embodiments of the present application, and is set according to the processing logic of the original transaction, in other words, the scheduling logic can be set in the orchestration rule of the original transaction, for example, it can be serial scheduling or parallel scheduling.

[0117] S205, based on the target orchestration microservice, determining a processing result according to the output result of the target sub-transaction component.

[0118] Exemplarily, referring to Figure 6 As shown, after the target sub-transaction component is invoked by the target microservice to process the transaction request, the output result of the target sub-transaction component is returned to the target orchestration microservice, and then, based on the target orchestration microservice, the output result of each target sub-transaction component and the target orchestration rule are used to make a decision to obtain the processing result of the transaction request, which can be transaction success or need to be processed. It should be noted that, referring to the content of the distributed transaction processing layer shown in Table 3, the target orchestration rule includes the decision logic of the processing result.

[0119] The business processing method based on the distributed financial system provided in the embodiments of the present application classifies and processes the transaction request through the orchestration service to determine the corresponding target orchestration microservice, and further determines the target orchestration rule of the transaction request according to the target orchestration microservice, which presets the target sub-transaction component and the calling sequence thereof required to process the transaction request. Then, according to the target orchestration rule and the target microservice, the target sub-transaction component is remotely invoked, and the target sub-transaction component can pass the processing task to the target unit component through the local invocation mode based on the target microservice, and the target unit component also relies on the target microservice to locally invoke the function component to deeply process the transaction request, and then obtains the output result of each target sub-transaction component, and finally obtains the final processing result of the transaction request according to the output result of each target sub-transaction component.

[0120] In this way, the transaction request is flexibly routed to the corresponding microservice and its internal components for processing, making full use of the distributed and parallel processing capabilities of the microservice architecture; at the same time, the multi-level and progressive calling mode not only improves the processing efficiency, but also enhances the scalability and maintainability of the distributed financial system. In summary, this mode not only realizes the fine splitting, modular processing and efficient execution of transaction requests, but also provides efficient, flexible and reliable transaction processing capabilities for the distributed financial system based on the transaction processing mechanism of the orchestration service, effectively improving the overall performance and user experience of the distributed financial system.

[0121] In some embodiments, Figure 7 Another application scenario provided by the present application is shown in the schematic diagram, and the business processing method based on the distributed financial system provided by the embodiments of the present application can further include: Figure 7

[0122] S301, in the process of calling the target sub-transaction component to process the transaction request, if it is determined according to the preset processing logic that a message needs to be sent, event information is determined.

[0123] For example, in the process of calling the target sub-transaction component based on the target microservice to process the transaction request, based on the preset processing logic of the target sub-transaction component, the target unit component or the target function component, a message can be sent to other centers. When it is determined that a message needs to be sent, the target microservice can call the event registration component to determine the event information, which represents the detailed information of the event that needs to send the message. The event detailed information may, for example, include event name, event type, message template, target recipient, etc. The event registration component is a public component that can be called by a trigger component, which can be any component such as a sub-transaction component, a unit component or a function component.

[0124] For example, the event information is determined based on the event registration component, the preset event definition table and the component event binding table. The event definition table can represent the detailed information of all events that need to send messages, and the component event binding table can represent the events that can be triggered by each trigger component. Further, based on the target microservice, if it is determined that the trigger component needs to send a message in the process of calling the target sub-transaction component to process the transaction request, the event registration component is called, the event triggered by the trigger component is determined according to the component ID of the trigger component and the component event binding table, and then the event information is determined according to the triggered event and the event definition table.

[0125] ​It can be understood that the step of determining the need to send a message according to the preset processing logic indicates the need to send a message indicated by the processing logic, in other words, it can be regarded as collecting the message events that need to be sent in the processing process, and waiting for the subsequent message notification decision, and then uniformly sending the messages.

[0126] S302, based on the target microservice, generating a task identifier and task information of the event task according to the event information.

[0127] Exemplarily, the event task represents a task of sending a message corresponding to the event. The task identifier is used to uniquely represent the event task, which can be an ID of the event task. The task information is used to describe the event task, which can include, for example, the task identifier, the trigger microservice number, the trigger timestamp, the transaction flow and the flow number, the event information, and the like.

[0128] In one example, based on the target microservice, the key elements of the event described in the event information can be obtained, which can include, for example, the microservice number triggering the event, the event number, the trigger timestamp, the transaction flow and the flow number of the transaction request, and the like, which are not limited herein. Further, the task identifier and the task information of the event task can be generated according to the key elements of the event and a preset generation template. The preset generation template represents the generation manner of the task identifier and the task information, which can be set according to actual needs. For example, the generation template of the task identifier can be: table index + YYMMDD (timestamp) + event number - flow number - transaction flow - current page number.

[0129] S303, based on the target microservice, storing the task identifier into the first database table and writing the task information into the second database table.

[0130] Exemplarily, in the database of the distributed financial system, a first database table for storing the task identifier of the event task to be processed and a second database table for storing the task information of the event task to be processed can be preset. Further, based on the target microservice, the task identifier can be stored into the first database table and the task information can be written into the second database table.

[0131] In this way, when the distributed financial system processes the transaction request, each level of component can call the event registration component to generate the event task to be processed when determining the need to send a message based on the preset processing logic, so that the event task can be directly processed after the message notification decision based on the orchestration service, and the message sending of the distributed financial system is realized.

[0132] As mentioned above, with reference to Figure 5As shown, the distributed financial system can make a decision according to the output of each target sub-transaction component and the target orchestration rule to obtain a processing result of the transaction request, which can be, for example, a successful transaction or a need for a correction process. In this implementation manner, a message notification decision can be made according to the processing result to determine whether a message needs to be sent. After it is determined that a message needs to be sent, the following steps can be included:

[0133] S401, if it is determined according to the processing result that a message needs to be sent, the task identifier stored in the first database table is stored in the event submission queue based on the proxy service.

[0134] For example, the distributed financial system further includes a proxy service for processing event tasks to generate a message. The event submission queue is used to cache task identifiers and follows the first-in, first-out principle.

[0135] In one example, the processing result can indicate whether the transaction is successful or needs to be corrected. If the distributed financial system determines that the transaction is successful based on the orchestration service, it can determine that a message needs to be sent through the message notification decision, call the proxy service, and store the task identifier stored in the first database table in the event submission queue based on the preset event submission component in the proxy service.

[0136] S402, based on the proxy service, the first task identifier in the event submission queue is extracted, and the task information of the event task corresponding to the task identifier is determined according to the task identifier.

[0137] For example, the distributed financial system can extract the first task identifier in the event submission queue based on the preset scheduling service in the proxy service, and determine the task information of the event task corresponding to the task identifier from the second database table based on the extracted task identifier.

[0138] S403, based on the proxy service, a message is generated and pushed according to the task identifier and the task information.

[0139] For example, the distributed financial system can send the task identifier and the task information to the task processor of the proxy service based on the preset scheduling service in the proxy service, so that the task processor can generate and push a message based on the task identifier and the task information. It should be noted that the task processor is configured with a message generation rule.

[0140] In some possible implementation manners, the agent service can preset a plurality of task processors, each of which can be used to process an event task of a different type, and thus the task processor can be allocated to the event task according to the task identifier and the task information; the agent service is used to process the event task according to the allocated task processor, and generate and push a message. In this way, the task processor corresponding to the event task can be processed, and the accuracy and efficiency of message generation can be improved.

[0141] Optionally, the message pushing can be into a message pushing queue of the distributed financial system, so as to push the message to a subscription pushing center of the distributed financial system based on the message pushing queue, and push the message to other centers by the subscription pushing center.

[0142] Optionally, the agent service can further include a daemon process, which is used to submit an event task listened by the daemon process to the event submission queue and the second database table according to the PRXRPC interface, and preferentially process the event task sent by the PRXRPC interface based on the scheduling service. The event task sent by the PRXRPC interface represents the management of parameters of the distributed financial system, for example, can be a parameter addition event, and the accuracy of subsequent transaction processing can be ensured by preferentially processing the event task. It can be understood that the parameter center can send the event task of parameter management to the subscription pushing center, and the subscription pushing center triggers the event task of the agent service based on the PRXRPC interface.

[0143] The business processing method based on the distributed financial system provided in the embodiments of the present application can collect event tasks representing the need to send messages generated in the processing process of a transaction request, and sequentially schedule and process the event tasks based on an agent service after the transaction is successful, to generate and push a message. In this way, in the case of splitting and decoupling of a transaction request, the message can be split into event tasks allocated in different sub-transaction processing processes, and the agent service is used to uniformly schedule and process the event tasks after the transaction is successful, so as to push the message, and realize message notification under a distributed architecture.

[0144] In some embodiments, Figure 8 The flowchart of the business processing method of the distributed financial system provided in the present application Figure 3 , as shown in Figure 6 , before the plurality of target sub-transaction components corresponding to the transaction request are determined in step S101, the transaction request can be preprocessed to obtain transaction information necessary for subsequent transaction processing, as shown in Figure 8 The business processing method based on the distributed financial system provided in the embodiments of the present application can further include:

[0145] S501, acquiring a current accounting time based on the orchestration service in response to the transaction request.

[0146] The accounting time represents a time range followed in performing accounting, and the accounting time facilitates periodic settlement of accounts. The accounting time can be a day, a week, a month, a quarter, a year, etc., and can be set according to actual needs.

[0147] In one example, the distributed financial system can acquire a current system time based on the orchestration service in response to the transaction request, and determine the current accounting time according to the current system time. For example, a calculation value based on the system time can be used, such as midnight as the start of a new day. When it is determined that the system time has not reached midnight, a preset accounting time is used as the current accounting time.

[0148] S502, performing a modulo operation on the current accounting time based on the orchestration service to obtain a remainder value.

[0149] The distributed financial system can perform a modulo operation on the current accounting time based on the orchestration service to obtain a remainder value according to a preset modulo base. The modulo base is a positive integer used to determine the range or period of the transaction serial number, for example, 3. For example, the current accounting time can be converted into a numerical form and subjected to a modulo operation to obtain a remainder value.

[0150] S503, determining a key value corresponding to the remainder value according to the remainder value.

[0151] The distributed financial system has a preset key-value mapping table indicating the correspondence between the remainder value and the key value (key), so the key value corresponding to the remainder value can be determined based on the remainder value.

[0152] S504, adding one to the preset value corresponding to the key value as the transaction serial number of the transaction request.

[0153] The distributed financial system has a Remote Dictionary Server (Redis), and the Redis database has values (values) corresponding to different keys, so the value corresponding to the key can be found in the Redis, and the value can be incremented by one and returned to the orchestration service as the transaction serial number of the transaction request.

[0154] Optionally, based on the orchestration service, if it is determined that the type of the transaction request is daily batch processing, the current accounting time is updated; based on the orchestration service, a modulo operation is performed on the updated current accounting time to obtain an updated remainder value; and the preset value corresponding to the key value corresponding to the updated remainder value is set to zero.

[0155] Specifically, the above-mentioned daily cut batch processing refers to a process in which the system performs batch processing, settlement and archiving on all transaction data of the day at a specific time point of each day (usually midnight or a certain business specified time). Based on the orchestration service, a preset field in the transaction request can be parsed and verified to determine that the type of the transaction request is daily cut batch processing, the current accounting time can be set to the start time of the next accounting date to update the current accounting time, and the updated current accounting time can be taken modulo to obtain an updated remainder value. Finally, the value corresponding to the key in the Redis corresponding to the updated remainder value is set to 0.

[0156] The business processing method based on the distributed financial system provided by the embodiments of the present application is based on the orchestration service. The system first responds to a transaction request and obtains the current accounting time. Then, the current accounting time is taken modulo to obtain a remainder value, which is used to determine a specific key value. According to the key value, the system finds the corresponding preset value and adds one to it as the transaction serial number of the transaction request. If the type of the transaction request is daily cut batch processing, the system will update the current accounting time and take the updated time modulo again to obtain a new remainder value. Then, the system resets the preset value corresponding to the key value corresponding to the new remainder value to zero to prepare for the generation of a new transaction serial number.

[0157] On the one hand, through the modulo processing based on the current accounting time and the increment of the preset value, the system can efficiently generate a unique transaction serial number, which not only guarantees the uniqueness of the transaction serial number, but also makes the generation process fast and does not require additional database queries or complex calculations, thereby improving the efficiency of transaction processing. On the other hand, through the orchestration service, the transaction serial number generation logic is separated from the transaction processing logic, making the system maintenance simpler and easier to extend. On the other hand, since the generation of the transaction serial number is based on the current accounting time and the increment of the preset value, this process is concurrent and does not introduce race conditions, and by resetting the preset value, the system can ensure that after the daily cut processing, the generation of the new transaction serial number will not be affected by the previous transactions, thereby improving the reliability and accuracy of transaction processing.

[0158] In some embodiments, during the process of processing transaction requests based on various sub-transaction components, some business processing logic needs to generate an ordered serial number, for example, in a bank card opening transaction request, a bank card number needs to be generated. The business processing method based on the distributed financial system provided by the embodiments of the present application can further include:

[0159] The distributed financial system can preset multiple ordered sequence numbers in Redis, for example, sequence numbers increasing from left to right; then, based on the orchestration service, when it is determined that an ordered sequence number is needed, a distributed lock is acquired to guarantee the uniqueness of the sequence number, the first sequence number is obtained from Redis and removed, and then the distributed lock is released, and the processing flow of the execution sub-transaction is returned. If the sequence number cannot be obtained from Redis, it is determined whether the number of currently remaining sequence numbers in Redis is less than or equal to a preset threshold, if yes, the last generated sequence number is determined, and a preset number of numerical sequence values are generated based on the last generated sequence number, and the generated numerical sequence values are added to Redis from the tail end one by one. If an exception occurs in the transaction processing, for example, transaction failure or other abnormal situations, rollback needs to be performed, that is, the obtained sequence number is added to the first position.

[0160] The business processing method based on the distributed financial system provided by the embodiment of the application has the following advantages. On the one hand, through the ordered sequence number management of the distributed lock and Redis, the system ensures that each transaction can obtain a unique and ordered sequence number, avoiding sequence number conflicts and repetitions; at the same time, the efficient operation of the distributed lock and Redis enables the system to still quickly allocate sequence numbers in a concurrent environment, and will not become a bottleneck of transaction processing, thereby improving the concurrent processing capability of the entire system. On the other hand, the sequence number supplement mechanism and the abnormal rollback processing enhance the robustness of the system, and even in a high-concurrency or abnormal situation, the system can ensure the continuous supply and effective management of sequence numbers, avoiding transaction failures caused by insufficient or abnormal sequence numbers.

[0161] Figure 9 The structure diagram of the business processing apparatus based on the distributed financial system provided by the application is shown in FIG. 1, and the business processing apparatus based on the distributed financial system provided by the embodiment of the application can be applied to a distributed financial system. The apparatus includes: Figure 9

[0162] The determining module 601 is configured to determine, based on the orchestration service, a plurality of target sub-transaction components corresponding to a transaction request in response to the transaction request.

[0163] The processing module 602 is configured to process the transaction request by progressively calling the target sub-transaction components based on the orchestration service and target microservices corresponding to the target sub-transaction components, to obtain a processing result of the target transaction request. The progressive calling represents that the orchestration service calls the target sub-transaction components of the target microservices, the target sub-transaction components call target unit components, and the target unit components call target function components.

[0164] In a possible implementation, the determining module 601 is specifically configured to: ​

[0165] Based on the orchestration service, a target orchestration microservice corresponding to the transaction request is determined in response to the transaction request;

[0166] Based on the target orchestration microservice, a target orchestration rule of the transaction request is determined; wherein the target orchestration rule represents target sub-transaction components required by the transaction request, and a calling logic between the target sub-transaction components;

[0167] Based on the target orchestration microservice and the target orchestration rule, the target sub-transaction components are determined.

[0168] In a possible implementation, the determining module 601 is specifically configured to:

[0169] Based on the target orchestration microservice, the entry condition of each sub-transaction component included in the target orchestration rule is sequentially verified, and if it is determined that the sub-transaction component meets a preset sub-transaction entry condition, the sub-transaction component is determined as a target sub-transaction component corresponding to the transaction request.

[0170] In a possible implementation, the orchestration service includes a target orchestration microservice corresponding to the transaction request, and the processing module 602 is specifically configured to:

[0171] Based on the target orchestration microservice, a target sub-transaction component of the target microservice is remotely called to process the transaction request, and an output result of the target sub-transaction component is obtained;

[0172] In the process in which the target sub-transaction component processes the transaction request, based on the target microservice, a target unit component is locally called to process the transaction request; in the process in which the target unit component processes the transaction request, based on the target microservice, a target function component is locally called to process the transaction request;

[0173] Based on the target orchestration microservice, the processing result is determined according to the output result of the target sub-transaction component.

[0174] In a possible implementation, the orchestration service includes a target orchestration microservice corresponding to the transaction request, and the processing module 602 is specifically configured to:

[0175] In the process in which the target sub-transaction component processes the transaction request, if it is determined according to a preset processing logic that a message needs to be sent, event information is determined;

[0176] Based on the target microservice, a task identifier and task information of an event task are generated according to the event information;

[0177] Based on the target microservice, the task identifier is stored into a first database table, and the task information is written into a second database table.

[0178] In a possible implementation, the system further includes an agent service, and the processing module 602 is specifically configured to:

[0179] If it is determined according to the processing result that the message needs to be sent, based on the agent service, the task identifier stored in the first database table is stored into an event submission queue;

[0180] Based on the agent service, the first task identifier in the event submission queue is extracted, and according to the task identifier, the task information of the event task corresponding to the task identifier is determined;

[0181] Based on the agent service, the message is generated and pushed according to the task identifier and the task information.

[0182] In a possible implementation, the processing module 602 is specifically configured to:

[0183] According to the task identifier and the task information, a task processor is allocated for the event task;

[0184] Based on the agent service, the event task is processed according to the allocated task processor, and the message is generated and pushed.

[0185] In a possible implementation, the determining module 601 is specifically configured to:

[0186] Based on the orchestration service, the current accounting time is obtained in response to the transaction request;

[0187] Based on the orchestration service, the current accounting time is processed by taking remainder to obtain a remainder value;

[0188] According to the remainder value, a key value corresponding to the remainder value is determined;

[0189] A preset value corresponding to the key value is added by one, serving as a transaction serial number of the transaction request.

[0190] In a possible implementation, the determining module 601 is specifically configured to:

[0191] Based on the orchestration service, if it is determined that the type of the transaction request is daily cut batch processing, the current accounting time is updated;

[0192] Based on the orchestration service, the updated current accounting time is processed by taking remainder to obtain an updated remainder value;

[0193] Set the preset value corresponding to the key value corresponding to the updated remainder value to zero.

[0194] The business processing apparatus based on the distributed financial system provided in the embodiment can execute the method provided in the method embodiment, and has similar implementation principles and technical effects. Details are not described herein.

[0195] Figure 10 A structural schematic diagram of an electronic device provided in the present application is shown in FIG. 7. As shown in the figure, the electronic device 700 provided in the embodiment includes at least one processor 701 and a memory 702. Optionally, the electronic device 700 further includes a communication component 703. The processor 701, the memory 702, and the communication component 703 are connected through a bus. The distributed financial system can include a plurality of electronic devices. Figure 10

[0196] In the implementation process, the at least one processor 701 executes the computer execution instructions stored in the memory 702, so that the at least one processor 701 executes the method described above.

[0197] The specific implementation process of the processor 701 can refer to the method embodiment described above, and has similar implementation principles and technical effects. Details are not described herein.

[0198] In the above embodiment, it should be understood that the processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the application can be directly embodied as execution completed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0199] The memory can include a random access memory (RAM), and can also include a non-volatile memory (NVM), for example, at least one disk memory.

[0200] ​The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, the bus in the drawings of the present application does not limit to only one bus or one type of bus.

[0201] The present application also provides a computer program product, comprising a computer program, which, when executed by a processor, implements the method described above.

[0202] The present application also provides a computer readable storage medium, which stores computer execution instructions, and when a processor executes the computer execution instructions, the method described above is implemented.

[0203] The readable storage medium described above can be realized by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0204] An exemplary readable storage medium is coupled to the processor, so that the processor can read information from the readable storage medium, and can write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in the device.

[0205] The division of units is only a logical functional division, and in actual implementation, there can be another division manner, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0206] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0207] In addition, each functional unit in various embodiments of the application can be integrated into one processing unit, or each unit can exist physically, or two or more units can be integrated into one unit.

[0208] If the function is realized in the form of a software function 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 solutions of the application essentially or the part that contributes to the prior art or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the various embodiment methods of the application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0209] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware. The aforementioned program can be stored in a computer readable storage medium. The program executes to perform the steps of the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, and various media that can store program codes.

[0210] Finally, it should be noted that those skilled in the art, after considering the specification and practicing the application disclosed herein, will easily think of other embodiments of the application. The application is intended to cover any variations, uses, or adaptations of the application that follow the general principles of the application and include common knowledge or conventional technical means in the art that are not disclosed by the application, and is not limited to the precise structure described above and shown in the drawings, and various modifications and changes can be made without departing from the scope thereof. The scope of the application is only limited by the appended claims.

Claims

1. A business processing method based on a distributed financial system, characterized in that: The method is applied to a distributed financial system, the system including an orchestration service and multiple microservices, each microservice including multiple sub-transaction components, and the method includes: Based on the orchestration service, in response to a transaction request, determining a plurality of target sub-transaction components corresponding to the transaction request; Based on the orchestration service and the target microservice corresponding to the target sub-transaction component, the transaction request is processed by progressively calling the target sub-transaction component to obtain a processing result of the target transaction request; wherein the progressive calling represents the orchestration service calling the target sub-transaction component of the target microservice, the target sub-transaction component calling the target unit component, and the target unit component calling the target function component.

2. The method according to claim 1, characterized in that The determining, based on the orchestration service and in response to a transaction request, a plurality of target sub-transaction components corresponding to the transaction request includes: Based on the orchestration service, in response to the transaction request, determining a target orchestration microservice corresponding to the transaction request; Determining a target orchestration rule for the transaction request based on the target orchestration microservice; wherein the target orchestration rule represents the target sub-transaction components required for the transaction request, and the calling logic between the target sub-transaction components; The target sub-transaction component is determined based on the target orchestration microservice and the target orchestration rule.

3. The method according to claim 2, characterized in that The determining the target sub-transaction component based on the target orchestration microservice and the target orchestration rule includes: Based on the target orchestration microservice, entry condition verification is performed on each sub-transaction component included in the target orchestration rule in turn. If it is determined that the sub-transaction component meets the preset sub-transaction entry condition, the sub-transaction component is determined to be the target sub-transaction component corresponding to the transaction request.

4. The method according to claim 1, wherein The orchestration service includes a target orchestration microservice corresponding to the transaction request. The target microservice corresponding to the target sub-transaction component, based on the orchestration service and the target microservice, processes the transaction request by progressively calling the target sub-transaction component to obtain a processing result of the target transaction request, including: Based on the target orchestration microservice, remotely call the target sub-transaction component of the target microservice, process the transaction request, and obtain the output result of the target sub-transaction component; Wherein, in the process of the target sub-transaction component processing the transaction request, the target unit component is locally called based on the target microservice to process the transaction request; in the process of the target unit component processing the transaction request, the target function component is locally called based on the target microservice to process the transaction request; Based on the target orchestration microservice, the processing result is determined according to the output result of the target sub-transaction component.

5. The method according to claim 1, wherein The orchestration service includes a target orchestration microservice corresponding to the transaction request, and the method further includes: In the process of calling the target sub-transaction component to process the transaction request, if it is determined according to the preset processing logic that a message needs to be sent, then determining event information; Based on the target microservice and according to the event information, generate a task identifier and task information of the event task; Based on the target microservice, the task identifier is stored in a first database table, and the task information is written into a second database table.

6. The method according to claim 5, characterized in that The system further includes an agent service, and the method further includes: If it is determined according to the processing result that a message needs to be sent, the task identifier stored in the first database table is stored in the event submission queue based on the proxy service; Based on the proxy service, extract the first task identifier in the event submission queue, and determine the task information of the event task corresponding to the task identifier according to the task identifier; Based on the proxy service, a message is generated and pushed according to the task identifier and task information.

7. The method according to claim 6, characterized in that The generating and pushing a message based on the proxy service and according to the task identifier and task information includes: Allocating a task processor for the event task according to the task identifier and task information; Based on the proxy service, the event task is processed according to the assigned task processor, and the message is generated and pushed.

8. The method according to any one of claims 1 to 7, characterized in that Before determining the multiple target sub-transaction components corresponding to the transaction request, the method includes: Based on the orchestration service, in response to the transaction request, obtaining a current accounting time; Based on the arrangement service, performing remainder processing on the current accounting time to obtain a remainder value; Determine the key value corresponding to the remainder value according to the remainder value; The preset value corresponding to the key value is increased by one to serve as the transaction serial number of the transaction request.

9. The method according to claim 8, characterized in that After determining the key value corresponding to the remainder value according to the remainder value, the method includes: If, based on the orchestration service, it is determined that the type of the transaction request is daily batch processing, updating the current accounting time; Based on the orchestration service, performing remainder processing on the updated current accounting time to obtain an updated remainder value; The preset value corresponding to the key value corresponding to the updated remainder value is set to zero.

10. A business processing device based on a distributed financial system, characterized in that: The apparatus is applied to a distributed financial system, the system including an orchestration service and multiple microservices, each microservice including multiple sub-transaction components, and the apparatus includes: a determination module, configured to determine, based on the orchestration service and in response to a transaction request, a plurality of target sub-transaction components corresponding to the transaction request; A processing module is configured to process the transaction request based on the orchestration service and the target microservice corresponding to the target sub-transaction component by progressively calling the target sub-transaction component to obtain a processing result of the target transaction request; wherein the progressive calling represents the orchestration service calling the target sub-transaction component of the target microservice, the target sub-transaction component calling the target unit component, and the target unit component calling the target function component.

11. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 9 when executed by a processor.

Images