CN106874076A - Distributed transaction processing method - Google Patents
Distributed transaction processing method Download PDFInfo
- Publication number
- CN106874076A CN106874076A CN201710043404.2A CN201710043404A CN106874076A CN 106874076 A CN106874076 A CN 106874076A CN 201710043404 A CN201710043404 A CN 201710043404A CN 106874076 A CN106874076 A CN 106874076A
- Authority
- CN
- China
- Prior art keywords
- subtransaction
- issued transaction
- node
- transaction node
- message
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/465—Distributed object oriented systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
- Multi Processors (AREA)
Abstract
The invention discloses a kind of distributed transaction processing method, including：One of issued transaction node in multiple issued transaction nodes receives affairs and starts request, and will start the corresponding affairs of request with affairs and be divided into some subtransactions；One of issued transaction node performs predetermined one of subtransaction, and remaining subtransaction is written into local data base, and the subtransaction in local data base is distributed into message queue；Message queue pushes subtransaction to remaining issued transaction node, corresponding subtransaction is written to the local data base of remaining issued transaction node, and after success flag is received from remaining issued transaction node, corresponding subtransaction is deleted from queue；Remaining issued transaction node is obtained from respective local data base and performs corresponding subtransaction, and after the completion of execution, corresponding subtransaction is deleted from local data base.The present invention can be quickly processed affairs, and ensure that the uniformity of affairs.
Description
Technical field
The present invention relates to data processing technique, more specifically, it relates to distributed transaction processing method.
Background technology
SaaS platforms are the platforms for runing saas softwares.SaaS providers informationization is built for enterprise required for all nets
Network infrastructure and software, hardware running platform, and it is responsible for a series of services such as implementation, the maintenance in later stage of all early stages, enterprise
Industry need not buy software and hardware, build computer room, recruitment IT personnel, you can by internet use information system.SaaS is a kind of soft
Part placement model, its application aims at network and pays and design, and is easy to user to pass through internet trustship, deployment and access.
It is big for saas platform service amount, it is necessary to underlying services are deployed on multiple servers respectively, but due to many
Can't be linked up between platform server, therefore, the problem of inconsistency of affairs can be produced again.
The content of the invention
In view of the shortcomings of the prior art, it is an object of the invention to provide a kind of distributed transaction processing method, energy
It is enough that affairs are quickly processed, and ensure that the uniformity of affairs.
To achieve the above object, the invention provides following technical scheme：
A kind of distributed transaction processing method, including：
One of issued transaction node in multiple issued transaction nodes receives affairs and starts request, and will be opened with the affairs
It is dynamic to ask corresponding affairs to be divided into some subtransactions；
One of issued transaction node performs predetermined one of subtransaction, and remaining subtransaction is written into this
Ground database；
One of issued transaction node after subtransaction has been performed, inquiry local data base in subtransaction, and will this
Subtransaction in ground database is distributed to message queue, and deletes corresponding subtransaction from local data base after distribution；
The message queue pushes subtransaction to remaining issued transaction node, and is received from remaining issued transaction node
After success flag, corresponding subtransaction is deleted from queue；
Subtransaction is write respective local data by described remaining issued transaction node after corresponding subtransaction is received
Storehouse；
Described remaining issued transaction node is obtained from respective local data base and performs corresponding subtransaction, and is being performed
After the completion of, corresponding subtransaction is deleted from local data base.
Preferably, the message queue uses RabbitMQ message queues.
Preferably, one of issued transaction node is sent out after the corresponding subtransaction of successful execution to message queue
Send confirmation message；After message queue receives confirmation message, message queue pushes subtransaction to remaining issued transaction node；Institute
One of issued transaction node is stated when corresponding subtransaction is performed not successfully, is sent to message queue and is cancelled message；Message
After queue receives cancellation message, message queue does not push subtransaction to remaining issued transaction node.
Preferably, also include：Subtransaction in message status confirmed service device query messages queue, if exist it is unconfirmed or
The subtransaction being cancelled, then inquire about the message status of correspondence subtransaction in one of issued transaction node, if corresponding
Message status have been identified, then to message queue transmission confirmation message.
Preferably, also include：
The subtransaction is written to respective transaction status by described remaining issued transaction node after corresponding subtransaction has been processed
Table；
When described remaining issued transaction node receives subtransaction from message queue, the transaction status table is inquired about, if existing,
The subtransaction that then will not receive is written to local data base；If not existing, local data base is written to pending.
Preferably, also include：
One of issued transaction node is obtained from mark processing server and includes some when being divided to affairs
The unique mark string of unique mark, and unique mark therein is added to each subtransaction correspondingly；When corresponding thing
Business treatment node is sent to mark processing server the unique mark after corresponding subtransaction has been performed；
The mark processing server inquires about the reception shape of corresponding unique mark after the scheduled time for sending unique mark string
State；If not received in the presence of at least one unique mark, corresponding issued transaction node is inquired about, and carry out according to Query Result
Corresponding treatment.
Preferably, it is described mark processing server record queries result, when same issued transaction querying node to uniquely
When the number of times of mark exceedes preset value, then the information of the issued transaction node is sent to monitoring server；The monitoring service
Device is transferred corresponding issued transaction node from standby issued transaction node repository and is replaced after corresponding information is received
Change.
Compared with prior art, it is an advantage of the invention that：
1st, each issued transaction node is only after corresponding subtransaction has been successfully processed, then deletes the affairs, so as to ensure whole
The uniformity of affairs；
2nd, each subtransaction is pushed to by corresponding issued transaction node by message queue, one side processing speed is fast, another
Aspect, ensure that each issued transaction node can be accurately received subtransaction；
3rd, with function for monitoring, by monitoring the cooperation between server and mark processing server, realize to each office
Manage node disposal ability monitoring, when certain issued transaction node frequently occur treatment it is slow or failure problem when, then from
Transfer corresponding issued transaction node in storehouse to be replaced, to ensure the smooth of issued transaction.
Brief description of the drawings
Fig. 1 is the system block diagram of distributing real time system system in embodiment 1；
Fig. 2 is the system block diagram of distributing real time system system in embodiment 2；
Fig. 3 is the system block diagram of distributing real time system system in embodiment 3；
Fig. 4 is the system block diagram of distributing real time system system in embodiment 4.
Specific embodiment
With reference to embodiment and accompanying drawing, the present invention is described in further detail, but embodiments of the present invention are not
It is only limitted to this.
Embodiment 1：
Distributing real time system system shown in Fig. 1, including some issued transaction nodes and message queue 130, only show in figure
Issued transaction node 110, issued transaction node 120, and with both as an example, being described in detail to the function of the system.
Wherein, issued transaction node 110 is configured with application server 111, database 112 and transaction server 113, office
Reason node 120 is configured with affairs receiver 121, local data base 122 and transaction server 113.Remaining office
Reason node is identical with the configuration of issued transaction node 120, therefore repeats no more.
After affairs startup request is received, will start with affairs please for application server 111 in issued transaction node 110
Ask corresponding affairs to be divided into some subtransactions, and subtransaction is written to local data base 112；Afterwards, transaction services
Device 113 performs predetermined one of subtransaction（This subtransaction is the top priority in whole affairs）, and by remaining sub- thing
Business is distributed to message queue 130；After message queue 130 receives subtransaction, returned to transaction server 113 and successfully marked
Know, transaction server 113 deletes corresponding subtransaction after mark is received from local data base 112.
The message queue can use RabbitQ message queues in the present embodiment, after message queue 130 receives subtransaction,
To the affairs the reception server 121 that subtransaction is pushed to issued transaction node 120, affairs the reception server 121 is successfully connecing
After receiving subtransaction, success flag is returned to message queue 130；After message queue 130 receives mark, phase is deleted from queue
The subtransaction answered.Affairs the reception server 121 will be written to local data base 122 to subtransaction；The thing of issued transaction node 120
The subtransaction that business processing server 123 is inquired about in local data base 122 by turns, when pending subtransaction is inquired, holds
The capable subtransaction.After transaction server 123 has been successfully processed subtransaction, then corresponding sub- thing is deleted from local data base
Business.
Therefore, the whole issued transaction flow of the system can be summarized as：
One of issued transaction node in multiple issued transaction nodes receives affairs and starts request, and will start with affairs and ask
Corresponding affairs are asked to be divided into some subtransactions；
One of issued transaction node performs predetermined one of subtransaction, and remaining subtransaction is written into local number
According to storehouse；
After subtransaction has been performed, the subtransaction in inquiry local data base and will be counted locally one of issued transaction node
Message queue is distributed to according to the subtransaction in storehouse, and deletes corresponding subtransaction from local data base after distribution；
Message queue pushes subtransaction to remaining issued transaction node, and is received successfully from remaining issued transaction node
After mark, corresponding subtransaction is deleted from queue；
Subtransaction is write respective local data base by remaining issued transaction node after corresponding subtransaction is received；
Remaining issued transaction node is obtained from respective local data base and performs corresponding subtransaction, and is performing completion
Afterwards, corresponding subtransaction is deleted from local data base.
Embodiment 2：
A kind of distributing real time system system based on embodiment 1, it is with the difference of embodiment 1：When issued transaction node
Transaction server 213 in 210 sends confirmation message after the corresponding subtransaction of successful execution to message queue 230；Disappear
After breath queue 230 receives confirmation message, subtransaction is pushed to issued transaction node 220.When transaction server 213 is not
During the corresponding subtransaction of successful execution, sent to message queue 230 and cancel message；After message queue receives cancellation message 230,
Then subtransaction is not pushed to issued transaction node 220.
In addition, in order to avoid transaction server 213 fails normally to send confirmation message to message queue 230 or takes
Message, and cause message queue 230 to hang up subtransaction for a long time, the system is also additionally arranged message status confirmed service device 240,
The message status confirmed service device 240 is configurable for the subtransaction in query messages queue, if existing unconfirmed or being taken
The subtransaction for disappearing, then in inquiry transaction processing server 213 correspondence subtransaction message status, if corresponding message status by
Confirm, then send confirmation message to message queue 230.In this way, by setting message status confirmed service device 240 so that message
Data can separate storage, reduce the coupling between issued transaction and Message Processing, it is to avoid messaging failure and cause affairs not
Situation about be processed in time occurs.
Embodiment 3：
A kind of distributing real time system system based on embodiment 1 or embodiment 2, it is with the difference of embodiment 1：The system
In, issued transaction node 320 is additionally arranged transaction status table 324, and the transaction status table 324 is configurable for each sub- thing of storage
The treatment record of business；Specifically, the transaction server 323 in issued transaction node 320 is processing corresponding subtransaction
Afterwards, the subtransaction is written to transaction status table 324, so as to generate corresponding historical record in transaction status table 324.Such as
This, when affairs the reception server 321 receives subtransaction from message queue 330, inquires about the transaction status table 324, if having deposited
In subtransaction in the same manner, then the subtransaction that will not receive is written to local data base（But equally returned into message queue 330
Work(is identified）；If not existing, local data base is written to pending.
Embodiment 4：
A kind of distributing real time system system based on embodiment 1 or embodiment 2 or embodiment 3, it exists with the difference of embodiment 1
In：The system is also additionally arranged mark processing server 440, and the mark processing server 440 is configured with N number of unique mark string, often
Include some unique marks in one unique mark string.Application server 411 in issued transaction node 410 is to affairs
When being divided, the unique mark string is obtained from mark processing server 440, and unique mark therein is added correspondingly
Add to each subtransaction, after the completion of addition, then will be added unique mark subtransaction send to mark processing server 440
Recorded.
When transaction server 413, transaction server 423 are after corresponding subtransaction has been performed, correspondence is obtained
Unique mark included in subtransaction, and the unique mark is sent to mark processing server 440（During transmission, for this only
One mark addition " processed mark "）.The identification server to application server 411 send the unique mark string when, to this
Unique mark string starts timing program；And after the meter full scheduled time, inquire about the reception state of corresponding unique mark；If in the presence of
At least one unique mark is not received, then inquire about all of issued transaction node, as an example, inquiry transaction treatment node
410th, issued transaction node 420.For example, first the local data base 422 in issued transaction node 420 is inquired about, if inquiry
The subtransaction not being performed to this is still trapped in local data base 422, it tries send thing to transaction server 423
Business triggering message, to notify that transaction server 423 obtains subtransaction and performs from local data base 422.If not from local
Subtransaction is inquired in database 422, is then sent directly to affairs the reception server to the subtransaction for being added unique mark
421, to be written to local data base 422 again.In this way, by above technical scheme, subtransaction can be avoided in processing procedure
It is middle to there is a problem of that subtransaction treatment is interrupted or lost.
In addition, the system is also configured with standby issued transaction node repository 460, the standby issued transaction node repository 460
In include N number of issued transaction node, disposal ability issued transaction node 420 or remaining issued transaction node are identical.Meanwhile,
Mark processing server 440 is additionally configured to record queries result, when in same issued transaction node, such as issued transaction node
420, when the number of times for inquiring unique mark exceedes preset value, then the information of the issued transaction node 420 is sent to monitoring and taken
Business device 450；Monitoring server 450 is transferred corresponding after corresponding information is received from standby issued transaction node repository 460
Issued transaction node be replaced.
Claims (7)
1. a kind of distributed transaction processing method, it is characterized in that, including：
One of issued transaction node in multiple issued transaction nodes receives affairs and starts request, and will be opened with the affairs
It is dynamic to ask corresponding affairs to be divided into some subtransactions；
One of issued transaction node performs predetermined one of subtransaction, and remaining subtransaction is written into this
Ground database；
One of issued transaction node after subtransaction has been performed, inquiry local data base in subtransaction, and will this
Subtransaction in ground database is distributed to message queue, and deletes corresponding subtransaction from local data base after distribution；
The message queue pushes subtransaction to remaining issued transaction node, and is received from remaining issued transaction node
After success flag, corresponding subtransaction is deleted from queue；
Subtransaction is write respective local data by described remaining issued transaction node after corresponding subtransaction is received
Storehouse；
Described remaining issued transaction node is obtained from respective local data base and performs corresponding subtransaction, and is being performed
After the completion of, corresponding subtransaction is deleted from local data base.
2. server service processing method according to claim 1, it is characterized in that, the message queue uses RabbitMQ
Message queue.
3. server service processing method according to claim 1, it is characterized in that, one of issued transaction node
After the corresponding subtransaction of successful execution, confirmation message is sent to message queue；After message queue receives confirmation message, message
Queue pushes subtransaction to remaining issued transaction node；One of issued transaction node is performed accordingly failed
During subtransaction, sent to message queue and cancel message；After message queue receives cancellation message, message queue is not to remaining thing
Business treatment node pushes subtransaction.
4. server service processing method according to claim 3, it is characterized in that, also include：Message status confirmed service
Subtransaction in device query messages queue, if there is subtransaction that is unconfirmed or being cancelled, inquires about one of affairs
The message status of correspondence subtransaction in treatment node, if corresponding message status have been identified, send to message queue and confirm
Message.
5. server service processing method according to claim 1, it is characterized in that, also include：
The subtransaction is written to respective transaction status by described remaining issued transaction node after corresponding subtransaction has been processed
Table；
When described remaining issued transaction node receives subtransaction from message queue, the transaction status table is inquired about, if existing,
The subtransaction that then will not receive is written to local data base；If not existing, local data base is written to pending.
6. server service processing method according to claim 1, it is characterized in that, also include：
One of issued transaction node is obtained from mark processing server and includes some when being divided to affairs
The unique mark string of unique mark, and unique mark therein is added to each subtransaction correspondingly；When corresponding thing
Business treatment node is sent to mark processing server the unique mark after corresponding subtransaction has been performed；
The mark processing server inquires about the reception shape of corresponding unique mark after the scheduled time for sending unique mark string
State；If not received in the presence of at least one unique mark, corresponding issued transaction node is inquired about, and carry out according to Query Result
Corresponding treatment.
7. server service processing method according to claim 6, it is characterized in that, the mark processing server record is looked into
Result is ask, when preset value is exceeded in the number of times of same issued transaction querying node to unique mark, then by the issued transaction section
The information of point is sent to monitoring server；It is described to monitor server after corresponding information is received, from standby issued transaction
Corresponding issued transaction node is transferred in node repository to be replaced.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710043404.2A CN106874076B (en) | 2017-01-21 | 2017-01-21 | Distributed transaction processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710043404.2A CN106874076B (en) | 2017-01-21 | 2017-01-21 | Distributed transaction processing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106874076A true CN106874076A (en) | 2017-06-20 |
| CN106874076B CN106874076B (en) | 2019-08-30 |
Family
ID=59158867
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710043404.2A Active CN106874076B (en) | 2017-01-21 | 2017-01-21 | Distributed transaction processing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106874076B (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108229909A (en) * | 2017-12-14 | 2018-06-29 | 四川虹慧云商科技有限公司 | A kind of resident's transaction methods |
| CN108900356A (en) * | 2018-07-25 | 2018-11-27 | 郑州云海信息技术有限公司 | A kind of cloud service dispositions method and system |
| CN108965457A (en) * | 2018-08-02 | 2018-12-07 | 郑州云海信息技术有限公司 | A kind of message delivery method of distributed cluster system, device, equipment and medium |
| CN110134735A (en) * | 2019-04-10 | 2019-08-16 | 阿里巴巴集团控股有限公司 | The storage method and device of distributed transaction log |
| CN110457157A (en) * | 2019-08-05 | 2019-11-15 | 腾讯科技（深圳）有限公司 | Distributed transaction abnormality eliminating method, device, computer equipment and storage medium |
| CN111679892A (en) * | 2020-06-04 | 2020-09-18 | 中国建设银行股份有限公司 | Distributed transaction processing method, device, equipment and medium |
| CN112181674A (en) * | 2019-07-04 | 2021-01-05 | 深圳市观麦网络科技有限公司 | Distributed transaction processing method based on RabbitMQ |
| CN112492019A (en) * | 2020-11-24 | 2021-03-12 | 上海优扬新媒信息技术有限公司 | Message pushing method and device, electronic equipment and storage medium |
| WO2021155496A1 (en) * | 2020-02-04 | 2021-08-12 | Honeywell International Inc. | Transaction based processing using asynchronous microservices |
| CN113268449A (en) * | 2021-03-03 | 2021-08-17 | 浪潮云信息技术股份公司 | Distributed file migration method and system based on object storage |
| WO2021259240A1 (en) * | 2020-06-22 | 2021-12-30 | 中兴通讯股份有限公司 | Distributed transaction processing method, terminal and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105183879A (en) * | 2015-09-22 | 2015-12-23 | 浪潮集团有限公司 | Method for distributed database to keep transactional consistency under cloud computation |
| CN105512244A (en) * | 2015-11-30 | 2016-04-20 | 北京京东尚科信息技术有限公司 | Database transaction processing method and device based on message queue |
| CN105824842A (en) * | 2015-01-07 | 2016-08-03 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and system |
| CN106168915A (en) * | 2016-04-25 | 2016-11-30 | 云南电网有限责任公司昆明供电局 | Distributed system architecture data process consistency ensuring method |
| CN106325978A (en) * | 2015-06-19 | 2017-01-11 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and apparatus |
-
2017
- 2017-01-21 CN CN201710043404.2A patent/CN106874076B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105824842A (en) * | 2015-01-07 | 2016-08-03 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and system |
| CN106325978A (en) * | 2015-06-19 | 2017-01-11 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and apparatus |
| CN105183879A (en) * | 2015-09-22 | 2015-12-23 | 浪潮集团有限公司 | Method for distributed database to keep transactional consistency under cloud computation |
| CN105512244A (en) * | 2015-11-30 | 2016-04-20 | 北京京东尚科信息技术有限公司 | Database transaction processing method and device based on message queue |
| CN106168915A (en) * | 2016-04-25 | 2016-11-30 | 云南电网有限责任公司昆明供电局 | Distributed system architecture data process consistency ensuring method |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108229909A (en) * | 2017-12-14 | 2018-06-29 | 四川虹慧云商科技有限公司 | A kind of resident's transaction methods |
| CN108229909B (en) * | 2017-12-14 | 2022-01-18 | 四川虹信软件股份有限公司 | Resident transaction processing method |
| CN108900356A (en) * | 2018-07-25 | 2018-11-27 | 郑州云海信息技术有限公司 | A kind of cloud service dispositions method and system |
| CN108965457A (en) * | 2018-08-02 | 2018-12-07 | 郑州云海信息技术有限公司 | A kind of message delivery method of distributed cluster system, device, equipment and medium |
| CN110134735A (en) * | 2019-04-10 | 2019-08-16 | 阿里巴巴集团控股有限公司 | The storage method and device of distributed transaction log |
| CN112181674A (en) * | 2019-07-04 | 2021-01-05 | 深圳市观麦网络科技有限公司 | Distributed transaction processing method based on RabbitMQ |
| CN110457157B (en) * | 2019-08-05 | 2021-05-11 | 腾讯科技（深圳）有限公司 | Distributed transaction exception handling method and device, computer equipment and storage medium |
| CN110457157A (en) * | 2019-08-05 | 2019-11-15 | 腾讯科技（深圳）有限公司 | Distributed transaction abnormality eliminating method, device, computer equipment and storage medium |
| WO2021155496A1 (en) * | 2020-02-04 | 2021-08-12 | Honeywell International Inc. | Transaction based processing using asynchronous microservices |
| CN111679892A (en) * | 2020-06-04 | 2020-09-18 | 中国建设银行股份有限公司 | Distributed transaction processing method, device, equipment and medium |
| WO2021259240A1 (en) * | 2020-06-22 | 2021-12-30 | 中兴通讯股份有限公司 | Distributed transaction processing method, terminal and computer readable storage medium |
| CN112492019A (en) * | 2020-11-24 | 2021-03-12 | 上海优扬新媒信息技术有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN113268449A (en) * | 2021-03-03 | 2021-08-17 | 浪潮云信息技术股份公司 | Distributed file migration method and system based on object storage |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106874076B (en) | 2019-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106874076A (en) | Distributed transaction processing method | |
| EP2321908B1 (en) | Method and system for message processing | |
| KR101623663B1 (en) | Method and system to maintain strong consistency of distributed replicated contents in a client/server system | |
| JP2562865B2 (en) | Communication device and communication method between at least one user and at least one server | |
| EP1659733B1 (en) | Apparatus and method for network management based on the simple network management protocol | |
| CN100536417C (en) | Grid licensing server and fault tolerant grid system and method of use | |
| EP0467546A2 (en) | Distributed data processing systems | |
| CN108132830A (en) | A kind of method for scheduling task, apparatus and system | |
| JP2005004243A (en) | Database backup method, program for making computer execute this method, database backup system, data server, and management server | |
| CN106506490B (en) | A kind of distributed computing control method and distributed computing system | |
| CN107005426A (en) | A kind of life cycle management method of virtual network function, and device | |
| CN105471700B (en) | A kind of methods, devices and systems of Message Processing | |
| WO2019231645A1 (en) | Change notifications for object storage | |
| US8141103B2 (en) | Solution for modifying a queue manager to support smart aliasing which permits extensible software to execute against queued data without application modifications | |
| CN110825505B (en) | Task scheduling method, device, computer equipment and storage medium | |
| CN108733515A (en) | Dispatching method, file backup method, device and the storage medium of file backup | |
| JP5507368B2 (en) | SNMP agent device and setting undo method | |
| JP5353714B2 (en) | Server system and its event message transmission method | |
| JP2008124977A (en) | Method, apparatus, and program of message delivery | |
| JP3542812B2 (en) | Distributed processing equipment | |
| JP2005092872A (en) | Service processing system, its processing method and its processing program | |
| CN104301240B (en) | Data transmission method and system | |
| EP3346671B1 (en) | Service processing method and equipment | |
| CN104680307B (en) | A kind of item transaction treating method and apparatus | |
| CN111316606A (en) | Optimized reconciliation in controller-switch networks |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200409 Address after: 310051 Room 902, Building B, 459 Yanmai Road, Xixing Street, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: Botu Shandao Network Technology Co.,Ltd. Address before: 310012, room 121, No. 8004, Xixi street, Xihu District, Zhejiang, Hangzhou, Wensanlu Road Patentee before: ZHEJIANG PEIHONG NETWORK TECHNOLOGY Co.,Ltd. |
|
| TR01 | Transfer of patent right |