CN107622119A - A kind of distributed integration across database keeps the method and system of transaction consistency - Google Patents
A kind of distributed integration across database keeps the method and system of transaction consistency Download PDFInfo
- Publication number
- CN107622119A CN107622119A CN201710861940.3A CN201710861940A CN107622119A CN 107622119 A CN107622119 A CN 107622119A CN 201710861940 A CN201710861940 A CN 201710861940A CN 107622119 A CN107622119 A CN 107622119A
- Authority
- CN
- China
- Prior art keywords
- business
- branch
- activity
- business activity
- main
- 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.)
- Pending
Links
Abstract
The invention discloses the method and system that a kind of distributed integration across database keeps transaction consistency, main business activity table and branch's business activity table are established in main business system, registers main business activity and all branch's business activities, and start business activity；Branch's operation system performs branch's business activity, establishes current business active state record sheet, persistence preserves current activity state, and sends active state to main business system；Main business system persistence preserves the execution data of main business activity and branch's industry activity, and the business activity operation timing of failure is operated again.Ensure that distributed structure/architecture system integration across database can be kept all the time during transaction operation the coherence request of data, can more effectively solve the problems, such as integration across database distributed transaction uniformity.The present invention keeps the method and system of transaction consistency as a kind of distributed integration across database, is widely used in technical field of the computer network.
Description
Technical field
The present invention relates to technical field of the computer network, more particularly to a kind of distributed integration across database to keep transaction consistency
Method and system.
Background technology
At present, Distributed Services framework is very popular, for electric business field.His the advantages of, does not just speak more
, but with the increase of clustered machine, the scale of cluster is also increasing, and the service scale carried with cluster is also increasingly
Greatly, the processing of affairs is caused also just to become increasingly complex, it is possible to which an affairs are related to more services of n, even if well imagining again
Excellent scheme also is difficult to the so complicated affairs of processing, it is easy to the problem of affairs are inconsistent be present.
The content of the invention
In order to solve the above-mentioned technical problem, it is an object of the invention to provide a kind of distributed integration across database to keep consistent affairs
The method and system of property.
The technical solution adopted in the present invention is：A kind of method that distributed integration across database keeps transaction consistency, it is wrapped
Include：Main business activity table and branch's business activity table are established in main business system, registers main business activity and all branch's industry
Business activity, and start business activity；Branch's operation system performs branch's business activity, establishes current business active state record
Table, persistence preserves current activity state, and sends active state to main business system；Main business system persistence preserves main business
Business activity and the execution data of branch's industry activity, the business activity operation timing of failure is operated again.
Further, branch's operation system performs branch's business activity, establishes current business active state record sheet, holds
Longization preserves current activity state, and includes to main business system transmission active state step：Branch's operation system performs branch
Business activity, current business active state record sheet is established, record traffic active state, is forever protected operation data if success
Deposit to branch's Service Database；Return information is to main business system if failure.
Further, the main business system persistence preserves the execution data of main business activity and working activity, to failure
Business activity operation timing carry out weight operating procedure include：The main business system persistence preserves main business activity and working
The execution data of activity, the business activity operation to failure carry out permanence preservation, resend and instruct to branch's operation system,
Branch's industry system re-executes branch's business activity, and until branch, business activity runs succeeded, and permanence preserves.
The system that a kind of distributed integration across database keeps transaction consistency, it is used to implement above-mentioned distributed integration across database guarantor
Hold transaction consistency, it is characterised in that：It includes main business system and branch's operation system, and the main business system includes：
Primary database：For storing main business activity table and branch's business activity table, the activity of registration main business, all branch's business are lived
It is dynamic；Business activity manager：For managing the execution of all business activities, and to the number of success and failure operation in implementation procedure
According to progress persistence preservation；Timer：For being operated to the business activity operation timing of failure again, until failure business is lived
Dynamic operation execution operates successfully again untill；Branch's operation system includes：Business activity actuator：For performing branch's business
Activity；Branch data storehouse：Current business active state is preserved for persistence；Feedback unit：For to main business system feedback
Current business active state.
Further, the branch system also includes judging unit：It is used for if success if by operation data persistence extremely
Branch's Service Database；Return information is to main business system if failure.
Further, main business system also includes retransmission unit, and it is used to resend business activity to branch's operation system.
The beneficial effects of the invention are as follows：By recording the implementation status of each business activity, failure is performed to each activity
Reverse operating registration is done, and persistence is carried out to the data of success and failure operation in business activity implementation procedure and remains to data
In storehouse, the business activity operation timing of failure is operated again, it is ensured that distributed structure/architecture system integration across database carries out transaction operation
When can keep the coherence requests of data all the time, can more effectively solve the problems, such as integration across database distributed transaction uniformity.
Brief description of the drawings
The embodiment of the present invention is described further below in conjunction with the accompanying drawings：
Fig. 1 is the flow chart of the method that distributed integration across database keeps transaction consistency in the present invention；
Fig. 2 is the schematic diagram of the system that distributed integration across database keeps transaction consistency in the present invention.
Embodiment
It should be noted that in the case where not conflicting, the feature in embodiment and embodiment in the application can phase
Mutually combination.
As shown in figure 1, a kind of method that distributed integration across database keeps transaction consistency, it includes：
Main business activity table and branch's business activity table are established in main business system, registers main business activity and all points
Branch business activity, and start business activity；
Main business effort scale is registered with the unique mark of business activity, beginning state, done state, and (business activity is handled
Failure, not at the end for the treatment of mechanism), branch's service number, main business activity creation time, the Status Change time, completed
Branch service execution return to operation, repeat to submit, unfinished branch's service execution submits operation.
Branch's business activity table is registered with branch movable mark, the main business activity ID, branch's Service name, performs submission
, can after carrying out unserializing by the value or method name, submission or the rollback method of return action correspond to the serializing value of parameter
Obtain entity object, branch's business activity creation time.
Branch's operation system performs branch's business activity, establishes current business active state record sheet, and persistence, which preserves, to be worked as
Preceding active state, and send active state to main business system；
Owner's business activity ID, affiliated main business activity ID are recorded in current business active state record sheet, is submitted
Method name, current activity state, activity creation time, active state change time.
Main business system persistence preserves the execution data of main business activity and branch's industry activity, the business activity to failure
Operation timing is operated again.Triggered time, every 5 minutes triggering timed tasks are defined, timed task is realized before inquiry 15 minutes
To preceding 2 small time all unfinished main business activities, operation again is performed to these operations until all main business activities execution into
Work(.
Preferred embodiment is further used as, branch's operation system performs branch's business activity, establishes current industry
Business active state record sheet, persistence preserves current activity state, and includes to main business system transmission active state step：Point
Branch operation system performs branch's business activity, establishes current business active state record sheet, record traffic active state, if success
Then by operation data persistence to branch's Service Database；Return information is to main business system if failure.
Specifically, the activity of registration main business, all branch's business activities, and start business activity.Branch's business is performed to live
Dynamic A, data X persistences are preserved into (local matter of A business) and perform branch business activity B, data Y persistences are preserved into (B industry
The local matter of business) persistence preservation Y failures, X data are performed inverse operations (rollback) by business activity manager, and make rollback number
According to persistence.
Preferred embodiment is further used as, the main business system persistence preserves main business activity and working activity
Execution data, to failure business activity operation timing carry out weight operating procedure include：The main business system persistence is protected
The execution data of main business activity and working activity are deposited, the business activity operation to failure carries out permanence preservation, resends
Instruction re-executes branch's business activity to branch's operation system, branch's industry system, and until branch, business activity runs succeeded, and
Permanence preserves.
Specifically, the activity of registration main business, all branch's business activities, and start business activity.Branch's business is performed to live
Dynamic A, preserves (local matter of A business) by data X persistences, performs branch business activity B, and data Y persistences are preserved into (B
The local matter of business), persistence preserves Y failures, and business activity manager compensates operation to Y, until Y data is successfully held
Turn to only long.
The system that a kind of distributed integration across database keeps transaction consistency, it is used to implement above-mentioned distributed integration across database guarantor
Hold transaction consistency, it is characterised in that：It includes main business system and branch's operation system, and the main business system includes：
Primary database：For storing main business activity table and branch's business activity table, the activity of registration main business, all branch's business are lived
It is dynamic；Business activity manager：For managing the execution of all business activities, and to the number of success and failure operation in implementation procedure
According to progress persistence preservation；Timer：For being operated to the business activity operation timing of failure again, until failure business is lived
Dynamic operation execution operates successfully again untill；Branch's operation system includes：Business activity actuator：For performing branch's business
Activity；Branch data storehouse：Current business active state is preserved for persistence；Feedback unit：For to main business system feedback
Current business active state.
Preferred embodiment is further used as, the branch system also includes judging unit：It is used for will if success
Operation data persistence is to branch's Service Database；Return information is to main business system if failure.
Preferred embodiment is further used as, main business system also includes retransmission unit, and it is used to resend business
Activity is to branch's operation system.
Above is the preferable implementation to the present invention is illustrated, but the invention is not limited to the implementation
Example, those skilled in the art can also make a variety of equivalent variations on the premise of without prejudice to spirit of the invention or replace
Change, these equivalent deformations or replacement are all contained in the application claim limited range.
Claims (6)
1. a kind of method that distributed integration across database keeps transaction consistency, it is characterised in that
It includes：
Main business activity table and branch's business activity table are established in main business system, registers main business activity and all branch's industry
Business activity, and start business activity；
Branch's operation system performs branch's business activity, establishes current business active state record sheet, and persistence preserves current living
Dynamic state, and send active state to main business system；
Main business system persistence preserves the execution data of main business activity and branch's industry activity, and the business activity to failure operates
Timing is operated again.
2. the method that distributed integration across database according to claim 1 keeps transaction consistency, it is characterised in that：Described point
Branch operation system performs branch's business activity, establishes current business active state record sheet, and persistence preserves current activity state,
And include to main business system transmission active state step：
Branch operation system performs branch's business activity, establishes current business active state record sheet, record traffic active state,
By operation data persistence to branch's Service Database if success；Return information is to main business system if failure.
3. the method that distributed integration across database according to claim 1 keeps transaction consistency, it is characterised in that：The master
Operation system persistence preserves the execution data of main business activity and working activity, and the business activity operation timing of failure is carried out
Weight operating procedure includes：
The main business system persistence preserves the execution data of main business activity and working activity, and the business activity to failure is grasped
Make to carry out permanence preservation, resend instruction to branch's operation system, branch's industry system and re-execute branch's business activity, directly
Run succeeded to branch's business activity, and permanence preserves.
4. the system that a kind of distributed integration across database keeps transaction consistency, it is used to implement any one of the claims 1 to 3
Described distributed integration across database keeps transaction consistency, it is characterised in that：It includes main business system and business system of branch
System,
The main business system includes：
Primary database：For storing main business activity table and branch's business activity table, the activity of registration main business, all branch's business
Activity；
Business activity manager：For managing the execution of all business activities, and to successful and failure operation in implementation procedure
Data carry out persistence preservation；
Timer：For being operated to the business activity operation timing of failure again, until failure business activity operation performs weight
Untill operating successfully；
Branch's operation system includes：
Business activity actuator：For performing branch's business activity；
Branch data storehouse：Current business active state is preserved for persistence；
Feedback unit：For to main business system feedback current business active state.
5. the system that distributed integration across database according to claim 4 keeps transaction consistency, it is characterised in that：Described point
Subsystem also includes judging unit：It is used for operation data persistence to branch's Service Database if success；If failure
Then return information is to main business system.
6. the system that distributed integration across database according to claim 5 keeps transaction consistency, it is characterised in that：Main business
System also includes retransmission unit, and it is used to resend business activity to branch's operation system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710861940.3A CN107622119A (en) | 2017-09-21 | 2017-09-21 | A kind of distributed integration across database keeps the method and system of transaction consistency |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710861940.3A CN107622119A (en) | 2017-09-21 | 2017-09-21 | A kind of distributed integration across database keeps the method and system of transaction consistency |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107622119A true CN107622119A (en) | 2018-01-23 |
Family
ID=61089980
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710861940.3A Pending CN107622119A (en) | 2017-09-21 | 2017-09-21 | A kind of distributed integration across database keeps the method and system of transaction consistency |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107622119A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108596768A (en) * | 2018-05-09 | 2018-09-28 | 神州数码融信软件有限公司 | A kind of distributed transaction processing method, apparatus and system |
| CN111324668A (en) * | 2020-02-18 | 2020-06-23 | 中国联合网络通信集团有限公司 | Database data synchronous processing method and device and storage medium |
| CN113342481A (en) * | 2021-07-07 | 2021-09-03 | 中国工商银行股份有限公司 | Transaction state confirmation method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106168915A (en) * | 2016-04-25 | 2016-11-30 | 云南电网有限责任公司昆明供电局 | Distributed system architecture data process consistency ensuring method |
| CN106775959A (en) * | 2016-12-06 | 2017-05-31 | 上海亿账通互联网科技有限公司 | Distributed transaction processing method and system |
-
2017
- 2017-09-21 CN CN201710861940.3A patent/CN107622119A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106168915A (en) * | 2016-04-25 | 2016-11-30 | 云南电网有限责任公司昆明供电局 | Distributed system architecture data process consistency ensuring method |
| CN106775959A (en) * | 2016-12-06 | 2017-05-31 | 上海亿账通互联网科技有限公司 | Distributed transaction processing method and system |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108596768A (en) * | 2018-05-09 | 2018-09-28 | 神州数码融信软件有限公司 | A kind of distributed transaction processing method, apparatus and system |
| CN111324668A (en) * | 2020-02-18 | 2020-06-23 | 中国联合网络通信集团有限公司 | Database data synchronous processing method and device and storage medium |
| CN111324668B (en) * | 2020-02-18 | 2023-11-21 | 中国联合网络通信集团有限公司 | Database data synchronous processing method, device and storage medium |
| CN113342481A (en) * | 2021-07-07 | 2021-09-03 | 中国工商银行股份有限公司 | Transaction state confirmation method and device |
| CN113342481B (en) * | 2021-07-07 | 2024-03-26 | 中国工商银行股份有限公司 | Transaction state confirmation method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106850746B (en) | The method and device of smooth service upgrading | |
| CN103312549B (en) | A kind of office management method and device and system | |
| CN103473318B (en) | A kind of distributed transaction support method towards memory data grid | |
| US20130097130A1 (en) | Method and system for resolving data inconsistency | |
| US8713163B2 (en) | Monitoring cloud-runtime operations | |
| US20130232113A1 (en) | Capturing And Restoring Database Session State | |
| CN107622119A (en) | A kind of distributed integration across database keeps the method and system of transaction consistency | |
| CN101262498B (en) | A distributed message call method and device | |
| CN104731943B (en) | A kind of server and data processing method | |
| US20040255182A1 (en) | Recovery guarantees for general multi-tier applications | |
| WO2020036879A1 (en) | In situ triggered function as a service within a service mesh | |
| CN106407021A (en) | Queue-based business request processing method | |
| JP3888827B2 (en) | Program replacement system, distributed processing system, and program replacement method | |
| JP2017517785A5 (en) | ||
| CN108230089A (en) | A kind of online order processing method, system and device | |
| US20160087759A1 (en) | Tuple recovery | |
| CN106462475B (en) | System and method for supporting the distributed data structure in distributed data grid | |
| CN107277022A (en) | Processes Tag method and device | |
| CN102413166B (en) | Distributed transaction method and system thereof | |
| CN107295030A (en) | A kind of method for writing data, device, data processing method, apparatus and system | |
| CN107844566B (en) | Dump control method and system | |
| CN110737510A (en) | Block device management system | |
| US8095826B1 (en) | Method and apparatus for providing in-memory checkpoint services within a distributed transaction | |
| US7716523B2 (en) | End-to-end transactional protection for requests in a web application | |
| EP3352418B1 (en) | Data processing status monitoring 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180123 |