CN113052687B - Transaction route distribution method and related device - Google Patents
Transaction route distribution method and related device Download PDFInfo
- Publication number
- CN113052687B CN113052687B CN202110486052.4A CN202110486052A CN113052687B CN 113052687 B CN113052687 B CN 113052687B CN 202110486052 A CN202110486052 A CN 202110486052A CN 113052687 B CN113052687 B CN 113052687B
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000009826 distribution Methods 0.000 title claims abstract description 36
- 238000012545 processing Methods 0.000 claims abstract description 40
- 238000013507 mapping Methods 0.000 claims abstract description 15
- 238000003860 storage Methods 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 3
- 230000009467 reduction Effects 0.000 claims description 3
- 238000004519 manufacturing process Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000002407 reforming Methods 0.000 description 3
- 238000004088 simulation Methods 0.000 description 3
- 230000007423 decrease Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000004308 accommodation Effects 0.000 description 1
- 230000001419 dependent effect 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
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000000087 stabilizing effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
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 route 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 or not, wherein the key domain information is used for identifying a front transaction with 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 a transaction request to a system for processing the front-end transaction according to the system identifier; the association relation is used for identifying a mapping relation between a system identifier corresponding to a system for processing the front-end transaction and key domain information corresponding to the front-end 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 front transaction and the follow-up 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 route distribution method and a related device.
Background
With the vigorous development of internet technology, people's life style has been greatly changed. In the industries of shopping, diet, travel, accommodation, medical treatment, financial services and the like, the online mode is gradually changed from the former offline mode to the online mode. With this, the system access volume increases explosively, so that some systems, such as a system employing a single architecture or a Service-oriented architecture (SOA), may not be able to carry, and downtime may occur.
Disclosure of Invention
Aiming at the problems, the application provides a transaction route distribution method and a related device, which are used for reducing the probability of downtime of a system.
In a first aspect of the present application, there is provided a transaction route distribution method, the method comprising:
receiving a transaction request;
judging whether the transaction request carries key domain information or not, wherein the key domain information is used for identifying a front transaction with 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 front-end transaction according to the system identifier; the association relation is used for identifying a mapping relation between a system identifier corresponding to a system for processing the front transaction and key domain information corresponding to the front transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing a 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, the new system being different from an architecture of the old system.
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 a transaction having a dependency relationship;
and configuring key domain information for the pre-transaction in the old system.
Optionally, the distributing the transaction request to a target system includes:
the transaction request is randomly distributed to the new system or the old system.
Optionally, if a plurality of transaction requests are acquired within a fixed time, the distributing the transaction requests to the target system includes:
distributing a part of the transaction requests in the plurality of transaction requests to the new system according to the distribution proportion, and distributing the rest transaction requests except the part of the transaction requests to the old system.
Optionally, the method further comprises:
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 comprises:
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, distributing the transaction request to the old system, wherein the first failure threshold is smaller than the second failure threshold.
In a second aspect of the present application, there is provided a transaction route distribution device, the device 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 or not, and the key domain information is used for identifying a front transaction with 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 yes, and distributing the transaction request to a system for processing the front-end transaction according to the system identifier; the association relation is used for identifying a mapping relation between a system identifier corresponding to a system for processing the front transaction and key domain information corresponding to the front transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing a 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 storing a computer program for executing the method of the above aspect.
Compared with the prior art, the above technical scheme has the advantages that:
the embodiment of the application provides a transaction route distribution method, which is characterized in that a route component is added in a plurality of systems running in parallel so as to distribute transactions to the plurality of systems through the route component. After receiving the transaction request, the routing component can judge whether the transaction request is a front transaction or a subsequent transaction according to whether the transaction request carries the key domain information because the key domain information can represent the front transaction with the dependency relationship with the transaction request. If the transaction request carries key domain information, the transaction request is indicated to be a follow-up transaction. In order to distribute multiple transactions with dependencies to the same system for processing, when the system receives the front-end transaction, an association relationship between key domain information of the front-end transaction and a system identifier is established, so that the system identifier of the front-end transaction processing system can be acquired according to the association relationship and the key domain information carried by the transaction request, the transaction request is distributed to the transaction system according to the system identifier, and the front-end transaction with the dependencies 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 front-end transaction, the current transaction request can be distributed to any system, namely a target system, and the association relation between the system identification of the target system and the key domain information of the current transaction request is established, so that all the follow-up transactions with the dependency relation with the current transaction can be distributed to the target system, and the front-end transaction and the follow-up transactions with the dependency relation are distributed to the same system for processing.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a transaction route distribution method provided herein;
FIG. 2 is a schematic diagram of a transaction route distribution device provided herein;
fig. 3 is a block diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the present invention better understood by those skilled in the art, the following description will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The problem of downtime of the system is that the access quantity of the system is overlarge, so that the access quantity of each system can be reduced through parallel operation of a plurality of systems, and the probability of downtime of the system is reduced. However, in the financial service industry, some transactions have dependencies, and if the dependent transactions are processed through different systems, the different systems are mutually independent, and data between the different systems are not shared, so that subsequent transactions cannot be completed.
For example, if the transaction request submitted by the user for applying the credit card is processed in the system a, the related information of the user and the credit card is stored in the system a, and if the transaction request of the user for performing the card swiping payment by using the credit card is distributed to the system B, the system B cannot process the transaction request at this time because the system B does not have the related information of the user and the credit card, which results in failure of the transaction at this time.
Based on the method, the transaction route distribution method is provided, and is used for improving the success rate of transactions while reducing the probability of downtime of the system.
As an example, a routing component can be added that is associated with multiple systems running in parallel to distribute transactions for the multiple systems. In order to distribute multiple transactions with dependencies to the same system for processing, the routing component may determine 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 payment by swiping a card using a credit card depends on having a credit card first, the key domain information is the credit card.
Therefore, the routing component can take whether the transaction request carries the key domain information as a judgment basis, and if the transaction request carries the key domain information, the routing component indicates that the transaction needs to depend on the related information of the previous transaction (hereinafter referred to as the pre-transaction), and can distribute the transaction request to a system for processing the pre-transaction for processing. If the transaction request does not carry key domain information, the transaction request can be distributed to any system for processing, wherein the key domain information indicates that the transaction does not need the related information of the front transaction. 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, by running multiple systems in parallel, the access amount of each system can be reduced, and compared with using only one system, the probability of downtime of the system is reduced. The embodiment of the present application is not particularly limited to the relationship between the multiple systems, and for example, may be a system with the same architecture, or may be a system with a different architecture.
In order to make the above objects, features and advantages of the present application more comprehensible, embodiments accompanied with figures and detailed description are described in further detail below.
Referring to fig. 1, fig. 1 is a flow chart of a transaction route distribution method provided herein, which may include the following steps 101-104.
S101: a transaction request is received.
The transaction request may be a request for applying a two-dimensional code, a request for applying a loan, a request for payment by a two-dimensional code, etc., which is not particularly limited in this application.
In the following, taking only one system to process a plurality of transaction requests as an example, after the user a sends a transaction request for applying a two-dimension code with a payment function to the system, the system distributes the two-dimension code for payment to the user a, and stores related information, such as account information, balance information and the like of the user a. After the user A sends a payment transaction request to the system according to the two-dimension code, the system can further process the transaction only by acquiring the related information of the user A according to the two-dimension code.
For the transaction, the transaction can be continued only by relying on the front transaction, that is, the user A applies the related information corresponding to the transaction of the two-dimensional code with the payment function to the system, so that the transaction and the front 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 among different systems is not shared.
S102: and judging whether the transaction request carries key domain information or not.
In order to distribute multiple transactions with a dependency relationship to the same system for processing, after receiving a transaction request, the transaction request may be judged to determine whether the transaction request has a dependency relationship with other transactions, and the transaction having a dependency relationship with the transaction request is generally a transaction occurring before the transaction, that is, a front-end transaction. The pre-transaction is a precondition for initiating the subsequent transaction, and the subsequent transaction is realized by depending on the information generated by the pre-transaction, so that the association information between the transactions can be set as key domain information, for example, two-dimensional code information, credit card information and the like can be set as key domain information.
Therefore, the transaction request of the subsequent transaction carries key domain information, and whether the transaction is the front transaction or the subsequent transaction can be judged according to whether the transaction request carries the key domain information.
S103: if yes, acquiring a system identifier according to the key domain information and the association relation, and distributing a transaction request to a system for processing the front-end transaction according to the system identifier.
If the acquired transaction request has key domain information, the transaction request is a subsequent transaction, and the related information of the front transaction can be acquired according to the key domain information.
Continuing taking the example in S101 as an example, after receiving the two-dimension code transaction request with the payment function sent by the user a, the system determines that the transaction request is a front transaction, and takes the two-dimension code information distributed for the user a as 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 by acquiring the related information of the front transaction by the two-dimension code of the user A.
The association relation is used for identifying a mapping relation between a system identifier corresponding to a system for processing the front-end transaction and key domain information corresponding to the front-end transaction.
After the system receives the front-end transaction, the system identification is mapped with the key domain information corresponding to the front-end transaction, and the corresponding system identification can be acquired through the key domain information, so that the subsequent transaction can be distributed to the system for processing the front-end transaction, the fact that the transaction with the dependency relationship can be processed by the same system is achieved, and the success rate of the transaction is improved.
S104: 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.
If the acquired transaction request does not have key domain information, the transaction request is a front transaction, and the front transaction does not need to rely on related 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 taking the example in S101 as an example, after the system receives the two-dimension code transaction request with the payment function sent by the user a, the system determines that the transaction request is a front transaction, distributes the transaction request to any one system for processing, and takes the two-dimension code information distributed for the user a as key domain information. If the system A receives the transaction request, storing a mapping relation between the two-dimensional code information distributed by the user A and the system identifier of the system A, namely, storing an association relation for representing the relation between the system identifier corresponding to the system for processing the front transaction and the key domain information corresponding to the front transaction.
The embodiment of the application provides a transaction route distribution method, which is characterized in that a route component is added in a plurality of systems running in parallel so as to distribute transactions to the plurality of systems through the route component. After receiving the transaction request, the routing component can judge whether the transaction request is a front transaction or a subsequent transaction according to whether the transaction request carries the key domain information because the key domain information can represent the front transaction with the dependency relationship with the transaction request. If the transaction request carries key domain information, the transaction request is indicated to be a follow-up transaction. In order to distribute multiple transactions with dependencies to the same system for processing, when the system receives the front-end transaction, an association relationship between key domain information of the front-end transaction and a system identifier is established, so that the system identifier of the front-end transaction processing system can be acquired according to the association relationship and the key domain information carried by the transaction request, the transaction request is distributed to the transaction system according to the system identifier, and the front-end transaction with the dependencies 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 front-end transaction, the current transaction request can be distributed to any system, namely a target system, and the association relation between the system identification of the target system and the key domain information of the current transaction request is established, so that all the follow-up transactions with the dependency relation with the current transaction can be distributed to the target system, and the front-end transaction and the follow-up transactions with the dependency relation are distributed to the same system for processing.
During the upgrading and reforming of the system, the use of the system is generally required to be suspended, so that a user cannot use the system and the experience of the user is poor, and the upgrading and reforming of the system brings a new problem, namely, how to gradually replace the old system to bear the whole production transaction. Wherein the architecture of the new system is different from the old system.
Thus, prior to the new system being put into use, a pre-transaction in the old system may be identified, which is a transaction with a dependency relationship, i.e. the initial transaction of a subsequent transaction, so that the subsequent transaction may obtain information about the pre-transaction to complete the transaction. The key domain information is configured for the pre-transaction in the old system so as to judge whether the transaction is the pre-transaction or the subsequent transaction according to whether the transaction request carries the key domain information after the new system is put into use.
In the process of upgrading and reforming an old system, in order to ensure that the new system can stably operate, before the new system is put into production, the old system data are generally synchronized to the new system through data migration, the new system is subjected to trial operation in simulation environments such as a drilling environment, a quasi-production environment and the like for a period of time, and the new system is put into production operation formally after the system stably operates in the simulation environment.
However, the actual production environment is complex and variable, so that it is difficult for the simulation environment to simulate all production scenes. For example, some sudden scenarios such as bug (bug), artificial abnormal operation, network resources, read/write data (I/O) pressure, etc. may cause unpredictable system failures, and even if a new system stably runs in a simulated environment, a serious production safety threat event may occur in an actual production environment, which affects user experience.
Based on this, the embodiment of the application proposes 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 pre-transaction by the above-mentioned S101-S104 mode, so that the pre-transaction and the subsequent transaction are both processed by one system, and the success rate of the transaction is improved.
In S104, after the routing component identifies the current transaction request as 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 remaining transaction requests among the transaction requests may be distributed to the old system in addition to the transaction requests distributed to the new system.
The embodiment of the present application is not particularly limited to a preset dispensing ratio, and will be described by taking two modes as examples.
Mode one:
since the failure frequency may reflect the stability of the new system to some extent, such as the new system may be less stable during the early test operation, the failure frequency is higher and decreases as the system becomes more 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 smaller number of transaction requests are issued to the new system to debug the new system using the real data without affecting the normal transaction traffic. As the frequency of failures decreases, indicating that the new system is gradually stabilizing, the number of transactions distributed to the new system may be gradually increased.
Mode two:
and acquiring the fault frequency of the new system, if the fault frequency of the new system is lower than a first fault threshold value, indicating that the new system is stable, distributing subsequent transaction requests to the system, and if the fault frequency of the new system is higher than a second fault threshold value, indicating that the new system is not stable, and distributing the transaction requests to the old system. Wherein the first failure threshold is the 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 the new system input, a small amount of transaction requests can be distributed for the new system, so that the new system can use real data to debug, the new system gradually tends to be stable along with the progress of debugging, and the transaction requests can be distributed for the new system until the new system can fully bear the transaction requests, the old system is replaced, and the upgrading and reconstruction of the old system are completed.
In addition to providing a transaction route distribution method, the embodiment of the present invention further provides a transaction route distribution device, as shown in fig. 2, where the transaction route distribution device 200 includes a receiving unit 201, a judging unit 202, and an executing unit 203;
the receiving unit 201 is configured to receive a transaction request;
the judging unit 202 is configured to judge whether the transaction request carries key domain information, where the key domain information is used to identify a pre-transaction that has a dependency relationship with the transaction request;
the executing unit 203 is configured to obtain a system identifier according to the key domain information and the association relationship if yes, and distribute the transaction request to a system for processing the pre-transaction according to the system identifier; the association relation is used for identifying a mapping relation between a system identifier corresponding to a system for processing the front transaction and key domain information corresponding to the front transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing a 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 one possible implementation, the plurality of systems includes a new system and an old system, the new system being different from the old system in architecture.
As a possible implementation manner, the transaction route distribution device 200 further includes a configuration unit configured to:
identifying a pre-transaction in the old system, the pre-transaction being an initial transaction of a transaction having a dependency relationship;
and configuring key domain information for the pre-transaction in the old system.
As a possible implementation manner, the execution unit 203 is configured to:
the transaction request is randomly distributed to the new system or the old system.
As a possible implementation manner, if multiple transaction requests are acquired in a fixed time, the execution unit 203 is configured to:
distributing a part of the transaction requests in the plurality of transaction requests to the new system according to the distribution proportion, and distributing the rest transaction requests except the part of the transaction requests to the old system.
As a possible implementation manner, the transaction route distribution device 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 route distribution device 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, distributing the transaction request to the old system, wherein the first failure threshold is smaller than the second failure threshold.
The embodiment of the application provides a transaction route distribution device, which adds a route component through a plurality of systems running in parallel so as to distribute transactions to the plurality of systems through the route component. After receiving the transaction request, the routing component can judge whether the transaction request is a front transaction or a subsequent transaction according to whether the transaction request carries the key domain information because the key domain information can represent the front transaction with the dependency relationship with the transaction request. If the transaction request carries key domain information, the transaction request is indicated to be a follow-up transaction. In order to distribute multiple transactions with dependencies to the same system for processing, when the system receives the front-end transaction, an association relationship between key domain information of the front-end transaction and a system identifier is established, so that the system identifier of the front-end transaction processing system can be acquired according to the association relationship and the key domain information carried by the transaction request, the transaction request is distributed to the transaction system according to the system identifier, and the front-end transaction with the dependencies 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 front-end transaction, the current transaction request can be distributed to any system, namely a target system, and the association relation between the system identification of the target system and the key domain information of the current transaction request is established, so that all the follow-up transactions with the dependency relation with the current transaction can be distributed to the target system, and the front-end transaction and the follow-up transactions with the dependency relation are distributed to the same system for processing.
The embodiment of the present application further provides a computer device, referring to fig. 3, which shows a structural diagram of the computer device provided in the embodiment of the present application, as shown in fig. 3, where 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 of the transaction route distribution methods provided in the foregoing embodiments according to instructions in the program code.
An embodiment of the present application provides a computer readable storage medium storing a computer program for executing any one of the transaction routing distribution methods provided in the above embodiments.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points. The apparatus embodiments described above are merely illustrative, wherein the units and modules illustrated as separate components may or may not be physically separate. In addition, some or all of the units and modules can be selected according to actual needs to achieve the purpose of the embodiment scheme. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The foregoing is merely illustrative of the embodiments of this invention and it will be appreciated by those skilled in the art that variations and modifications may be made without departing from the principles of the invention, and it is intended to cover all modifications and variations as fall within the scope of the invention.
Claims (8)
1. A transaction route distribution method, the method comprising:
receiving a transaction request;
judging whether the transaction request carries key domain information or not, wherein the key domain information is used for identifying a front transaction with 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 front-end transaction according to the system identifier; the association relation is used for identifying a mapping relation between a system identifier corresponding to a system for processing the front transaction and key domain information corresponding to the front transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing a mapping relation between the key domain information corresponding to the transaction request and a system identifier corresponding to the target system; the target system is any one of a plurality of systems, wherein the systems comprise a new system and an old system, and the new system is different from the old system in architecture;
before the receiving the transaction request, the method further comprises:
identifying a pre-transaction in the old system, the pre-transaction being an initial transaction of a transaction having a dependency relationship;
and configuring key domain information for the pre-transaction in the old system.
2. The method of claim 1, wherein said distributing the transaction request to a target system comprises:
the transaction request is randomly distributed to the new system or the old system.
3. The method of claim 1, wherein if a plurality of transaction requests are acquired within a fixed time, the distributing the transaction requests to a target system comprises:
distributing a part of the transaction requests in the plurality of transaction requests to the new system according to the distribution proportion, and distributing the rest transaction requests except the part of the transaction requests to the old system.
4. A method according to claim 3, characterized in that the method further comprises:
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.
5. The method according to claim 1, wherein the method further comprises:
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, distributing the transaction request to the old system, wherein the first failure threshold is smaller than the second failure threshold.
6. A transaction route distribution device, which is characterized in that the device comprises a receiving unit, a judging unit, an executing unit and a configuration 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 or not, and the key domain information is used for identifying a front transaction with 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 yes, and distributing the transaction request to a system for processing the front-end transaction according to the system identifier; the association relation is used for identifying a mapping relation between a system identifier corresponding to a system for processing the front transaction and key domain information corresponding to the front transaction;
if not, distributing the transaction request to a target system, configuring key domain information corresponding to the transaction request, and storing a mapping relation between the key domain information corresponding to the transaction request and a system identifier corresponding to the target system; the target system is any one of a plurality of systems, wherein the systems comprise a new system and an old system, and the new system is different from the old system in architecture;
the configuration unit is used for identifying a pre-transaction in the old system before receiving the transaction request, wherein the pre-transaction is an initial transaction of a transaction with a dependency relationship; and configuring key domain information for the pre-transaction in the old system.
7. 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-5 according to instructions in the program code.
8. A computer readable storage medium, characterized in that the computer readable storage medium is adapted to store a computer program adapted to perform the method of any of claims 1-5.
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 CN113052687A (en) | 2021-06-29 |
| CN113052687B true 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 |
|---|---|
| CN113052687A (en) | 2021-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9514034B1 (en) | Ordered test execution to enable faster feedback | |
| CN108829581B (en) | Application program testing method and device, computer equipment and storage medium | |
| CN111309594B (en) | System testing method, device, equipment and storage medium | |
| US9870221B2 (en) | Providing code change job sets of different sizes to validators | |
| CN111181770A (en) | Resource allocation method, system, electronic equipment and storage medium | |
| US20200153645A1 (en) | Increasing processing capacity of processor cores during initial program load processing | |
| CN113064744A (en) | Task processing method and device, computer readable medium and electronic equipment | |
| CN109615384B (en) | Method, device and server for generating timeliness check rule | |
| CN110060140A (en) | Mass data account checking method, device, medium and computer equipment | |
| US20240045793A1 (en) | Method and system for scalable performance testing in cloud computing environments | |
| US20190333141A1 (en) | System and method for implementing customer exposure management tool | |
| US20230144084A1 (en) | Analysis of code coverage differences across environments | |
| US20220405659A1 (en) | Data-driven automated model impact analysis | |
| CN110781134A (en) | Data processing method and device, computer storage medium and electronic equipment | |
| CN114003510A (en) | Script testing method, device, equipment and medium based on Mock service | |
| CN113052687B (en) | Transaction route distribution method and related device | |
| CN110442455A (en) | A kind of data processing method and device | |
| CN115018621A (en) | Contract changing method, device, equipment and medium | |
| CN106878369B (en) | Service processing method and device | |
| CN114493561A (en) | Information interaction mode replacement method, device, equipment and storage medium | |
| CN115689763A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110008098B (en) | Method and device for evaluating operation condition of nodes in business process | |
| CN113900933A (en) | Test method and related device | |
| CN108255724B (en) | Method and system for testing transaction participants | |
| CN107123051B (en) | Resource synchronization method and device |
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 |