CN113052687A - Transaction routing distribution method and related device - Google Patents
Transaction routing distribution method and related device Download PDFInfo
- Publication number
- CN113052687A CN113052687A CN202110486052.4A CN202110486052A CN113052687A CN 113052687 A CN113052687 A CN 113052687A CN 202110486052 A CN202110486052 A CN 202110486052A CN 113052687 A CN113052687 A CN 113052687A
- Authority
- CN
- China
- Prior art keywords
- transaction
- transaction request
- domain information
- key domain
- distributing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000009826 distribution Methods 0.000 title claims abstract description 36
- 238000012545 processing Methods 0.000 claims abstract description 36
- 238000013507 mapping Methods 0.000 claims abstract description 15
- 238000004590 computer program Methods 0.000 claims description 4
- 238000003860 storage Methods 0.000 claims description 4
- 230000009467 reduction Effects 0.000 claims description 3
- 238000004519 manufacturing process Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 4
- 238000004088 simulation Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000004308 accommodation Effects 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000037213 diet Effects 0.000 description 1
- 235000005911 diet Nutrition 0.000 description 1
- 238000005553 drilling Methods 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001131 transforming effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/03—Credit; Loans; Processing thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K17/00—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations
- G06K17/0022—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisious for transferring data to distant stations, e.g. from a sensing device
- G06K17/0025—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisious for transferring data to distant stations, e.g. from a sensing device the arrangement consisting of a wireless interrogation device in combination with a device for optically marking the record carrier
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Abstract
The embodiment of the invention discloses a transaction routing distribution method and a related device, wherein the method comprises the steps of receiving a transaction request; judging whether the transaction request carries key domain information, wherein the key domain information is used for identifying a preposed transaction which has a dependency relationship with the transaction request; if yes, acquiring a system identifier according to the key domain information and the association relation, and distributing the transaction request to a system for processing the preposed transaction according to the system identifier; the incidence relation is used for identifying a mapping relation between a system identification corresponding to a system for processing the preposed transaction and key domain information corresponding to the preposed transaction; if not, distributing the transaction request to the target system, configuring key domain information corresponding to the transaction request, and storing the mapping relation between the key domain information corresponding to the transaction request and the system identifier corresponding to the target system; wherein the target system is any one of a plurality of systems. Therefore, the method and the device realize that the pre-transaction and the subsequent transaction with the dependency relationship are distributed to the same system for processing.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a transaction routing distribution method and a related device.
Background
With the vigorous development of internet technology, people's lifestyle has revolutionized greatly. In the industries of shopping, diet, travel, accommodation, medical treatment, financial service and the like, the traditional on-line mode is gradually changed into the on-line mode. With the explosive and drastic increase of the system access volume, some systems, such as a system adopting a single-body Architecture or a system adopting a Service-Oriented Architecture (SOA), may not be able to carry the data, and may be down.
Disclosure of Invention
In order to solve the above problems, the present application provides a transaction route distribution method and a related apparatus, which are used to reduce the probability of system downtime.
In a first aspect of the present application, there is provided a transaction routing distribution method, the method comprising:
receiving a transaction request;
judging whether the transaction request carries key domain information, wherein the key domain information is used for identifying a preposed transaction which has a dependency relationship with the transaction request;
if yes, acquiring a system identifier according to the key domain information and the association relation, and distributing the transaction request to a system for processing the preposed transaction according to the system identifier; the incidence relation is used for identifying a mapping relation between a system identification corresponding to a system for processing the preposed transaction and key domain information corresponding to the preposed transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing the mapping relation between the key domain information corresponding to the transaction request and a system identifier corresponding to the target system; wherein the target system is any one of a plurality of systems.
Optionally, the plurality of systems includes a new system and an old system, and the new system and the old system have different architectures.
Optionally, before the receiving the transaction request, the method further includes:
identifying a pre-transaction in the old system, the pre-transaction being an initial transaction of transactions having dependencies;
configuring key domain information for the pre-staged transaction in the old system.
Optionally, the distributing the transaction request to the target system includes:
randomly distributing the transaction request to the new system or the old system.
Optionally, if a plurality of transaction requests are obtained within a fixed time, the distributing the transaction requests to the target system includes:
and distributing a part of the transaction requests in the transaction requests to the new system according to a distribution ratio, and distributing the rest transaction requests except the part of the transaction requests to the old system.
Optionally, the method further includes:
acquiring the fault frequency of the new system;
and adjusting the distribution proportion according to the fault frequency, wherein the adjustment mode is that the distribution proportion is increased along with the reduction of the fault frequency.
Optionally, the method further includes:
acquiring the fault frequency of the new system;
the distributing the transaction request to a target system includes:
if the failure frequency is lower than a first failure threshold, distributing the transaction request to the new system; and if the failure frequency is higher than a second failure threshold value, distributing the transaction request to the old system, wherein the first failure threshold value is smaller than the second failure threshold value.
In a second aspect of the present application, a transaction routing distribution apparatus is provided, the apparatus including a receiving unit, a judging unit, and an executing unit;
the receiving unit is used for receiving a transaction request;
the judging unit is used for judging whether the transaction request carries key domain information, and the key domain information is used for identifying a preposed transaction which has a dependency relationship with the transaction request;
the execution unit is used for acquiring a system identifier according to the key domain information and the association relation if the key domain information and the association relation exist, and distributing the transaction request to a system for processing the preposed transaction according to the system identifier; the incidence relation is used for identifying a mapping relation between a system identification corresponding to a system for processing the preposed transaction and key domain information corresponding to the preposed transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing the mapping relation between the key domain information corresponding to the transaction request and a system identifier corresponding to the target system; wherein the target system is any one of a plurality of systems.
In a third aspect, the present application provides a computer device comprising a processor and a memory:
the memory is used for storing program codes and transmitting the program codes to the processor;
the processor is configured to perform the method of the above aspect according to instructions in the program code.
In a fourth aspect, the present application provides a computer readable storage medium for storing a computer program for performing the method of the above aspect.
Compared with the prior art, the technical scheme of the application has the advantages that:
the embodiment of the application provides a transaction routing distribution method, which is characterized in that a routing component is added to a plurality of systems running in parallel, so that transactions can be distributed to the systems through the routing component. After the routing component receives the transaction request, the key domain information can represent the preposed transaction which has a dependency relationship with the transaction request, so that whether the transaction request is the preposed transaction or the subsequent transaction can be judged according to whether the transaction request carries the key domain information or not. If the current transaction request carries the key domain information, the current transaction request is indicated to be a subsequent transaction. In order to distribute a plurality of transactions with dependency to the same system for processing, when the system receives the preposed transaction, the incidence relation between the key domain information of the preposed transaction and the system identification is established, so the system identification of the preposed transaction processing system can be obtained according to the incidence relation and the key domain information carried by the transaction request, the transaction request is distributed to the transaction system according to the system identification, and the preposed transaction with dependency and the subsequent transaction are distributed to the same system for processing. If the current transaction request does not carry key domain information, the current transaction request is indicated to be a pre-transaction, the current transaction request can be distributed to any system, namely a target system, and the association relationship between the system identifier of the target system and the key domain information of the current transaction request is established, so that subsequent transactions with the dependency relationship with the current transaction can be distributed to the target system, and the pre-transaction and the subsequent transactions with the dependency relationship are distributed to the same system to be processed.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow chart of a transaction routing distribution method provided herein;
FIG. 2 is a schematic diagram of a transaction routing distribution apparatus provided herein;
fig. 3 is a block diagram of a computer device according to an embodiment of the present disclosure.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The problem of system downtime is that because the access volume of the system is too large, the access volume of each system can be reduced by the parallel operation of a plurality of systems, so that the probability of system downtime is reduced. However, in the financial services industry, some transactions have dependencies, and if the transactions with dependencies are processed through different systems, the different systems are independent from each other, and data is not shared between the different systems, so that subsequent transactions cannot be completed.
For example, if the user submits a transaction request for applying for a credit card, which is processed in the system a, the information related to the user and the credit card is stored in the system a, and if the user subsequently uses the credit card to pay by swiping the card, the transaction request is distributed to the system B.
Based on the above, the application provides a transaction route distribution method, which is used for improving the success rate of transactions while reducing the probability of system downtime.
As an example, a routing component can be added and associated with multiple systems running in parallel to distribute transactions for the multiple systems. In order to distribute a plurality of transactions with dependency to the same system for processing, the routing component judges the received transaction request. The key domain information is used to identify whether there is a dependency relationship between transactions, and as in the previous example, the use of a credit card for card payment depends on having a credit card first, and the key domain information is the credit card.
Therefore, the routing component can use whether the transaction request carries the key domain information as a judgment basis, if the transaction request carries the key domain information, the fact that the transaction needs to depend on the related information of the previous transaction (hereinafter referred to as the preposed transaction) is explained, and the transaction request can be distributed to a system for processing the preposed transaction for processing. If the transaction request does not carry the key domain information, the transaction request does not need the related information of the preposed transaction, and the transaction request can be distributed to any system for processing. Therefore, the transaction with the dependency relationship can be processed by the same system, and the success rate of the transaction is improved.
It should be noted that the access amount of each system can be reduced by the parallel operation of a plurality of systems, and compared with the case of only using one system, the probability of the system going down is reduced. The embodiments of the present application do not specifically limit the relationship between multiple systems, and for example, the systems may be systems with the same architecture, or may be systems with different architectures.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, embodiments accompanying the drawings are described in detail below.
Referring to fig. 1, fig. 1 is a flowchart of a transaction routing distribution method provided in the present application, which may include the following steps 101-104.
S101: a transaction request is received.
The transaction request may be a request for applying for a two-dimensional code, a request for applying for a loan, a request for payment through a two-dimensional code, or the like, and this is not particularly limited in this application.
In the following, taking an example that only one system is adopted to process a plurality of transaction requests, after a user a sends a transaction request for applying for a two-dimensional code with a payment function to the system, the system distributes the two-dimensional code for payment to the user a and stores related information, such as account information and balance information of the user a. After the user A sends a transaction request for payment to the system according to the two-dimensional code, the system needs to acquire the relevant information of the user A according to the two-dimensional code, and then the transaction can be further processed.
For the transaction, the transaction can be continued only by relying on the preposed transaction, that is, the user a applies for the relevant information corresponding to the transaction of the two-dimensional code with the payment function to the system, so that the transaction and the preposed transaction have a dependency relationship, and if a plurality of transactions with the dependency relationship are distributed to a plurality of systems for processing, the subsequent transaction cannot be completed because data is not shared among different systems.
S102: and judging whether the transaction request carries key domain information.
In order to distribute a plurality of transactions having a dependency relationship to the same system for processing, after receiving a transaction request, a determination may be made as to whether the transaction request has a dependency relationship with other transactions, and a transaction having a dependency relationship with the current transaction request is generally a transaction occurring before the current transaction, that is, a preceding transaction. The pre-transaction is a precondition for initiating the subsequent transaction, the subsequent transaction is realized by relying on information generated by the pre-transaction, and the associated information between the transactions can be set as key domain information, for example, two-dimension code information, credit card information and the like can be set as the key domain information.
Therefore, the transaction request of the subsequent transaction carries the key domain information, and whether the transaction is a front-end transaction or a subsequent transaction can be judged according to whether the transaction request carries the key domain information.
S103: and if so, acquiring a system identifier according to the key domain information and the association relation, and distributing the transaction request to a system for processing the preposed transaction according to the system identifier.
If the acquired transaction request has the key domain information, the transaction request is a subsequent transaction, and the related information of the previous transaction can be acquired according to the key domain information.
Continuing with the example in S101, after receiving the two-dimensional code transaction request with payment function sent by the user a, the system determines that the transaction request is a pre-transaction, and uses the two-dimensional code information distributed for the user a as the key domain information. If the system receives a transaction request for payment sent according to the two-dimension code of the user A, the transaction request carries the two-dimension code of the user A as key domain information, so that the transaction request is a subsequent transaction, and the transaction can be completed only if the two-dimension code of the user A can acquire the related information of the previous transaction.
The incidence relation is used for identifying a mapping relation between a system identification corresponding to a system for processing the preposed transaction and key domain information corresponding to the preposed transaction.
After receiving the preposed transaction, the system maps the system identification with the key domain information corresponding to the preposed transaction, and the corresponding system identification can be obtained through the key domain information, so that the subsequent transaction can be distributed to a system for processing the preposed transaction, the transactions with the dependency relationship can be processed by the same system, and the success rate of the transaction is improved.
S104: if not, the transaction request is distributed to the target system, key domain information corresponding to the transaction request is configured, and the mapping relation between the key domain information corresponding to the transaction request and the system identification corresponding to the target system is stored.
If the acquired transaction request does not contain key domain information, the transaction request is a pre-transaction which does not need to depend on relevant information of other transactions, so that the transaction request can be distributed to any one of a plurality of systems running in parallel for processing, namely the transaction request is distributed to a target system for processing.
Continuing to take the example in S101 as an example, after receiving the two-dimensional code transaction request with payment function sent by the user a, the system determines that the transaction request is a pre-transaction, distributes the transaction request to any one of the systems for processing, and uses the two-dimensional code information distributed to the user a as the key domain information. If the system A receives the transaction request, the mapping relation between the two-dimension code information distributed for the user A and the system identifier of the system A is stored, namely the incidence relation between the system identifier corresponding to the system for representing and processing the preposed transaction and the key domain information corresponding to the preposed transaction is stored.
The embodiment of the application provides a transaction routing distribution method, which is characterized in that a routing component is added to a plurality of systems running in parallel, so that transactions can be distributed to the systems through the routing component. After the routing component receives the transaction request, the key domain information can represent the preposed transaction which has a dependency relationship with the transaction request, so that whether the transaction request is the preposed transaction or the subsequent transaction can be judged according to whether the transaction request carries the key domain information or not. If the current transaction request carries the key domain information, the current transaction request is indicated to be a subsequent transaction. In order to distribute a plurality of transactions with dependency to the same system for processing, when the system receives the preposed transaction, the incidence relation between the key domain information of the preposed transaction and the system identification is established, so the system identification of the preposed transaction processing system can be obtained according to the incidence relation and the key domain information carried by the transaction request, the transaction request is distributed to the transaction system according to the system identification, and the preposed transaction with dependency and the subsequent transaction are distributed to the same system for processing. If the current transaction request does not carry key domain information, the current transaction request is indicated to be a pre-transaction, the current transaction request can be distributed to any system, namely a target system, and the association relationship between the system identifier of the target system and the key domain information of the current transaction request is established, so that subsequent transactions with the dependency relationship with the current transaction can be distributed to the target system, and the pre-transaction and the subsequent transactions with the dependency relationship are distributed to the same system to be processed.
During upgrading and modifying the system, the use of the system generally needs to be suspended, so that a user cannot use the system, and the experience of the user is poor, so that a new problem is caused by upgrading and modifying the system, namely how to gradually replace the old system by the new system to undertake all production transactions. Wherein the new system has a different architecture than the old system.
Therefore, before the new system is put into use, the preposed transaction in the old system can be identified, and the preposed transaction is a transaction with dependency relationship, namely an initial transaction of a subsequent transaction, so that the subsequent transaction can acquire the related information of the preposed transaction to complete the transaction. And configuring key domain information for the preposed transaction in the old system so as to judge whether the transaction is the preposed transaction or the subsequent transaction by judging whether the transaction request carries the key domain information or not after the new system is put into use.
In the process of upgrading and transforming the old system, in order to ensure that the new system can stably operate, before the new system is put into production, the data of the old system is synchronized to the new system through data migration, the new system is tried to operate in a simulation environment such as a drilling environment, a quasi-production environment and the like for a period of time, and the system is put into production and operation formally after being stably operated in the simulation environment.
However, the actual production environment is complex and variable, so that the simulation environment is difficult to simulate all production scenes. For example, some sudden scenarios such as program bugs (bugs), human abnormal operations, network resources, Input/Output (I/O) pressure, etc. may cause unpredictable system failures, and even if a new system stably operates in a simulation environment in an actual production environment, an event seriously threatening production safety may occur, which affects user experience.
Based on this, the embodiment of the application provides that the new system and the old system run in parallel, if the new system and the old system run in parallel, the subsequent transaction can be accurately routed to the system for processing the preposed transaction in the manner of the foregoing S101-S104, so that the preposed transaction and the subsequent transaction are processed by one system, and the success rate of the transaction is improved.
In S104, after the routing component identifies that the current transaction request is a pre-transaction, the current transaction request may be randomly distributed to the new system or the old system, or a part of the transactions may be distributed to the new system and another part of the transactions may be distributed to the old system according to a preset distribution ratio.
Specifically, if a plurality of transaction requests are acquired within a fixed time, a part of the transaction requests may be distributed to the new system according to the distribution ratio, and the rest of the transaction requests in the transaction requests are distributed to the old system except the transaction request distributed to the new system.
The present embodiment does not specifically limit the preset dispensing ratio, and two modes are described below as examples.
The first method is as follows:
because the fault frequency can reflect the stable condition of the new system to a certain extent, if the new system is possibly not stable during the early commissioning, the fault frequency is higher, and the fault frequency is reduced as the system is gradually stable. Therefore, the fault frequency can be obtained, and the distribution proportion can be adjusted according to the fault frequency. For example, when the failure frequency is high, a small number of transaction requests are distributed to the new system, so that the new system can be debugged by using real data on the premise of not influencing normal transaction business. As the frequency of failure decreases, indicating that the new system is gradually settling, the number of transactions distributed to the new system may be gradually increased.
The second method comprises the following steps:
and acquiring the failure frequency of the new system, if the failure frequency of the new system is lower than a first failure threshold value, indicating that the new system is stable, distributing the subsequent transaction request to the system, and if the failure frequency of the new system is higher than a second failure threshold value, indicating that the new system is not stable, distributing the transaction request to the old system. Wherein the first failure threshold is a second failure threshold.
Therefore, whether the new system is stable or not can be judged according to the fault frequency of the new system, the new system is not stable at the initial stage of putting the new system into use, a small amount of transaction requests can be distributed to the new system, so that the new system can be debugged by using real data, the new system gradually tends to be stable along with the debugging, the transaction requests can be distributed to the new system in a large amount until the new system can bear all the transaction requests, the old system is replaced, and the upgrading and the reconstruction of the old system are completed.
In addition to the transaction route distribution method provided by the embodiment of the present invention, a transaction route distribution apparatus is also provided, as shown in fig. 2, the transaction route distribution apparatus 200 includes a receiving unit 201, a determining unit 202, and an executing unit 203;
the receiving unit 201 is configured to receive a transaction request;
the determining unit 202 is configured to determine whether the transaction request carries key domain information, where the key domain information is used to identify a pre-transaction having a dependency relationship with the transaction request;
the execution unit 203 is configured to, if yes, obtain a system identifier according to the key domain information and the association relationship, and distribute the transaction request to a system that processes the advanced transaction according to the system identifier; the incidence relation is used for identifying a mapping relation between a system identification corresponding to a system for processing the preposed transaction and key domain information corresponding to the preposed transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing the mapping relation between the key domain information corresponding to the transaction request and a system identifier corresponding to the target system; wherein the target system is any one of a plurality of systems.
As a possible implementation, the plurality of systems includes a new system and an old system, the new system having a different architecture than the old system.
As a possible implementation manner, the transaction routing distribution apparatus 200 further includes a configuration unit, configured to:
identifying a pre-transaction in the old system, the pre-transaction being an initial transaction of transactions having dependencies;
configuring key domain information for the pre-staged transaction in the old system.
As a possible implementation manner, the execution unit 203 is configured to:
randomly distributing the transaction request to the new system or the old system.
As a possible implementation manner, if multiple transaction requests are obtained within a fixed time, the execution unit 203 is configured to:
and distributing a part of the transaction requests in the transaction requests to the new system according to a distribution ratio, and distributing the rest transaction requests except the part of the transaction requests to the old system.
As a possible implementation manner, the transaction routing distribution apparatus 200 further includes an adjusting unit, configured to:
acquiring the fault frequency of the new system;
and adjusting the distribution proportion according to the fault frequency, wherein the adjustment mode is that the distribution proportion is increased along with the reduction of the fault frequency.
As a possible implementation manner, the transaction routing distribution apparatus 200 further includes an obtaining unit, configured to:
acquiring the fault frequency of the new system;
the execution unit 203 is configured to:
if the failure frequency is lower than a first failure threshold, distributing the transaction request to the new system; and if the failure frequency is higher than a second failure threshold value, distributing the transaction request to the old system, wherein the first failure threshold value is smaller than the second failure threshold value.
The embodiment of the application provides a transaction routing distribution device, which is convenient for distributing transactions for a plurality of systems through routing components by adding routing components to the systems running in parallel. After the routing component receives the transaction request, the key domain information can represent the preposed transaction which has a dependency relationship with the transaction request, so that whether the transaction request is the preposed transaction or the subsequent transaction can be judged according to whether the transaction request carries the key domain information or not. If the current transaction request carries the key domain information, the current transaction request is indicated to be a subsequent transaction. In order to distribute a plurality of transactions with dependency to the same system for processing, when the system receives the preposed transaction, the incidence relation between the key domain information of the preposed transaction and the system identification is established, so the system identification of the preposed transaction processing system can be obtained according to the incidence relation and the key domain information carried by the transaction request, the transaction request is distributed to the transaction system according to the system identification, and the preposed transaction with dependency and the subsequent transaction are distributed to the same system for processing. If the current transaction request does not carry key domain information, the current transaction request is indicated to be a pre-transaction, the current transaction request can be distributed to any system, namely a target system, and the association relationship between the system identifier of the target system and the key domain information of the current transaction request is established, so that subsequent transactions with the dependency relationship with the current transaction can be distributed to the target system, and the pre-transaction and the subsequent transactions with the dependency relationship are distributed to the same system to be processed.
An embodiment of the present application further provides a computer device, referring to fig. 3, which shows a structural diagram of a computer device provided in an embodiment of the present application, and as shown in fig. 3, the device includes a processor 310 and a memory 320:
the memory 310 is used for storing program codes and transmitting the program codes to the processor;
the processor 320 is configured to execute any one of the transaction routing distribution methods provided by the above embodiments according to instructions in the program code.
The embodiment of the application provides a computer-readable storage medium, which is used for storing a computer program, and the computer program is used for executing any transaction routing distribution method provided by the embodiment.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, and the units and modules described as separate components may or may not be physically separate. In addition, some or all of the units and modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing is directed to embodiments of the present invention, and it is understood that various modifications and improvements can be made by those skilled in the art without departing from the spirit of the invention.
Claims (10)
1. A transaction routing distribution method, the method comprising:
receiving a transaction request;
judging whether the transaction request carries key domain information, wherein the key domain information is used for identifying a preposed transaction which has a dependency relationship with the transaction request;
if yes, acquiring a system identifier according to the key domain information and the association relation, and distributing the transaction request to a system for processing the preposed transaction according to the system identifier; the incidence relation is used for identifying a mapping relation between a system identification corresponding to a system for processing the preposed transaction and key domain information corresponding to the preposed transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing the mapping relation between the key domain information corresponding to the transaction request and a system identifier corresponding to the target system; wherein the target system is any one of a plurality of systems.
2. The method of claim 1, wherein the plurality of systems comprises a new system and an old system, and wherein the new system is architecturally different from the old system.
3. The method of claim 2, wherein prior to said receiving a transaction request, said method further comprises:
identifying a pre-transaction in the old system, the pre-transaction being an initial transaction of transactions having dependencies;
configuring key domain information for the pre-staged transaction in the old system.
4. The method of claim 2, wherein said distributing the transaction request to a target system comprises:
randomly distributing the transaction request to the new system or the old system.
5. The method of claim 2, wherein distributing the transaction request to the target system if multiple transaction requests are obtained within a fixed time comprises:
and distributing a part of the transaction requests in the transaction requests to the new system according to a distribution ratio, and distributing the rest transaction requests except the part of the transaction requests to the old system.
6. The method of claim 5, further comprising:
acquiring the fault frequency of the new system;
and adjusting the distribution proportion according to the fault frequency, wherein the adjustment mode is that the distribution proportion is increased along with the reduction of the fault frequency.
7. The method of claim 2, further comprising:
acquiring the fault frequency of the new system;
the distributing the transaction request to a target system includes:
if the failure frequency is lower than a first failure threshold, distributing the transaction request to the new system; and if the failure frequency is higher than a second failure threshold value, distributing the transaction request to the old system, wherein the first failure threshold value is smaller than the second failure threshold value.
8. A transaction routing distribution device is characterized by comprising a receiving unit, a judging unit and an executing unit;
the receiving unit is used for receiving a transaction request;
the judging unit is used for judging whether the transaction request carries key domain information, and the key domain information is used for identifying a preposed transaction which has a dependency relationship with the transaction request;
the execution unit is used for acquiring a system identifier according to the key domain information and the association relation if the key domain information and the association relation exist, and distributing the transaction request to a system for processing the preposed transaction according to the system identifier; the incidence relation is used for identifying a mapping relation between a system identification corresponding to a system for processing the preposed transaction and key domain information corresponding to the preposed transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing the mapping relation between the key domain information corresponding to the transaction request and a system identifier corresponding to the target system; wherein the target system is any one of a plurality of systems.
9. A computer device, the device comprising a processor and a memory:
the memory is used for storing program codes and transmitting the program codes to the processor;
the processor is configured to perform the method of any of claims 1-7 according to instructions in the program code.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program for performing the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110486052.4A CN113052687B (en) | 2021-04-30 | 2021-04-30 | Transaction route distribution method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110486052.4A CN113052687B (en) | 2021-04-30 | 2021-04-30 | Transaction route distribution method and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113052687A true CN113052687A (en) | 2021-06-29 |
| CN113052687B CN113052687B (en) | 2024-02-02 |
Family
ID=76518118
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110486052.4A Active CN113052687B (en) | 2021-04-30 | 2021-04-30 | Transaction route distribution method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113052687B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108564470A (en) * | 2018-04-17 | 2018-09-21 | 北京天德科技有限公司 | The transaction distribution method of block is built in a kind of block chain parallel |
| US10732961B1 (en) * | 2017-12-02 | 2020-08-04 | Juniper Networks, Inc | Systems and methods for performing in-service software upgrades on active network devices |
| CN112070497A (en) * | 2020-09-09 | 2020-12-11 | 上海万向区块链股份公司 | Associated transaction rearrangement method, system and medium based on intelligent contract design |
-
2021
- 2021-04-30 CN CN202110486052.4A patent/CN113052687B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10732961B1 (en) * | 2017-12-02 | 2020-08-04 | Juniper Networks, Inc | Systems and methods for performing in-service software upgrades on active network devices |
| CN108564470A (en) * | 2018-04-17 | 2018-09-21 | 北京天德科技有限公司 | The transaction distribution method of block is built in a kind of block chain parallel |
| CN112070497A (en) * | 2020-09-09 | 2020-12-11 | 上海万向区块链股份公司 | Associated transaction rearrangement method, system and medium based on intelligent contract design |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113052687B (en) | 2024-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110782240B (en) | Business data processing method and device, computer equipment and storage medium | |
| CN108563567B (en) | Automated testing method, apparatus, device and computer readable storage medium | |
| CN109285069B (en) | Resource transfer method, device and server | |
| JP2012533824A (en) | Systems and methods for real-time batch account processing | |
| CN113505520A (en) | Method, device and system for supporting heterogeneous federated learning | |
| CN107038025B (en) | SOA architecture-based system calling method and device | |
| US20190333141A1 (en) | System and method for implementing customer exposure management tool | |
| CN106034148B (en) | Rapid information interaction method, local server, remote server and system | |
| CN110413421B (en) | Service data processing method and device, and transaction data processing method and device | |
| CN113052687A (en) | Transaction routing distribution method and related device | |
| CN114327802B (en) | Method, apparatus, device and medium for block chain access to data outside chain | |
| CN113657817B (en) | Transaction processing method and device, electronic equipment and readable storage medium | |
| CN112950355B (en) | Transaction data processing method and device | |
| CN113868139A (en) | Method and device for analyzing number making accuracy, electronic equipment and storage medium | |
| CN114493561A (en) | Information interaction mode replacement method, device, equipment and storage medium | |
| CN113900933A (en) | Test method and related device | |
| CN106878369B (en) | Service processing method and device | |
| CN111950770A (en) | Method and device for managing resource return auxiliary strategy and electronic equipment | |
| CN111127003B (en) | Wallet account payment method, device and storage medium | |
| CN112084106B (en) | Method and device for selecting test data, computing equipment and computer storage medium | |
| CN110827009B (en) | Fund transfer method and device based on account balance limit | |
| CN112994959B (en) | Service test control system, method, device and storage medium | |
| CN115689770A (en) | Construction method of asset hosting wind control model, risk assessment method and device | |
| CN116418873A (en) | Service processing method and device and electronic equipment | |
| CN117455469A (en) | Resource processing method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |