CN107277022A - Processes Tag method and device - Google Patents
Processes Tag method and device Download PDFInfo
- Publication number
- CN107277022A CN107277022A CN201710501482.2A CN201710501482A CN107277022A CN 107277022 A CN107277022 A CN 107277022A CN 201710501482 A CN201710501482 A CN 201710501482A CN 107277022 A CN107277022 A CN 107277022A
- Authority
- CN
- China
- Prior art keywords
- procedure call
- remote procedure
- call protocol
- solicited message
- thread
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- 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/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- 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/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Abstract
The embodiment of the present invention provides a kind of Processes Tag method and device.This method includes：By in the solicited message write-in First ray of remote procedure call protocol；Processing data storehouse affairs；If db transaction fails, the offset coordinates of the First ray are moved, the solicited message is processed to be finished the offset coordinates for identifying；If db transaction success, the solicited message is write in the second sequence；If the solicited message is successfully written in second sequence, the offset coordinates of the First ray are moved.The embodiment of the present invention improves the degree of accuracy of remote procedure call protocol and the service message of asynchronous queue by the way that queue technology is applied in the micro services cluster of pure remote procedure call protocol sync.
Description
Technical field
The present embodiments relate to communication technical field, more particularly to a kind of Processes Tag method and device.
Background technology
Remote procedure call protocol, is that one kind asks service by network from remote computer program, without
Solve the agreement of underlying network technology.Remote procedure call protocol assumes the presence of some host-host protocols, such as TCP or UDP, for communication
Information data is carried between program.In OSI network communication models, remote procedure call protocol spans transport layer and application
Layer.Remote procedure call protocol causes the application program developed including network distribution type multiprogram to be more prone to.Long-range mistake
Journey invocation protocol uses Client/Server pattern.Requestor is exactly a client computer, and service providing program is exactly one
Server.First, client calls process sends a recalls information for having a process parameter to service processes, then etc. to be answered
Information.In server end, process keeps sleep state untill recalls information is reached.When a recalls information is reached, service
Device obtains process parameter, and result of calculation sends reply message, then waits next recalls information, finally, client call enters
Journey receives reply message, obtains proceeding results, then calls execution to proceed.
But, the distributed post of processing thread one high-throughput of correspondence of a remote procedure call protocol, which is subscribed to, to disappear
The function of breath system, the function is used for the processing state for tracking the thread, if the processing line of multiple remote procedure call protocols
Cheng Bingfa is performed, and the distributed post for resulting in the need for substantial amounts of high-throughput is subscribed to the function of message system, remotely mistake is caused
The service message of journey invocation protocol and asynchronous queue is inaccurate.
The content of the invention
The embodiment of the present invention provides a kind of Processes Tag method and device, to improve remote procedure call protocol and asynchronous team
The degree of accuracy of the service message of row.
The one side of the embodiment of the present invention is to provide a kind of Processes Tag method, including：
By in the solicited message write-in First ray of remote procedure call protocol；
Processing data storehouse affairs；
If db transaction fails, the offset coordinates of the First ray are moved, the offset coordinates are used to identify
The solicited message is processed and finished；
If db transaction success, the solicited message is write in the second sequence；
If the solicited message is successfully written in second sequence, the offset coordinates of the First ray are moved.
The other side of the embodiment of the present invention is to provide a kind of Processes Tag device, including：
Writing module, for the solicited message of remote procedure call protocol to be write in First ray；
Processing module, for processing data storehouse affairs；
Mobile module, for when db transaction fails, the offset coordinates of the mobile First ray, the skew to be sat
Mark for identify the solicited message be processed finish；
If db transaction success, said write module writes the solicited message in the second sequence；
If the solicited message is successfully written in second sequence, the mobile module moves the First ray
Offset coordinates.
Processes Tag method and device provided in an embodiment of the present invention, is adjusted by the way that queue technology is applied to pure remote process
In the micro services cluster combined with protocol synchronization, the accurate of remote procedure call protocol and the service message of asynchronous queue is improved
Degree.
Brief description of the drawings
Fig. 1 is Processes Tag method flow diagram provided in an embodiment of the present invention；
The Processes Tag method flow diagram that Fig. 2 provides for another embodiment of the present invention；
Fig. 3 is the structure chart of Processes Tag device provided in an embodiment of the present invention；
The structure chart for the Processes Tag device that Fig. 4 provides for another embodiment of the present invention.
Embodiment
In order to prevent database from writing successfully, then write queue, but queue write-in failure returns to mistake, allows upstream weight
Examination, upstream may be abandoned, and cause the phenomenon of information drop-out, or database to write successfully, and what then full computer room was powered off shows
As occurring, that is to say, that we need to prevent that message must ensure in write-in queue when the affairs success of database, if
The affairs failure of database, message should not be appeared in queue, so certainly can not elder generation's write queue, then write database, otherwise
Allowing the distributed post of high-throughput to subscribe to message system supports the phenomenon of the rollback of message to occur.The present embodiment propose only according to
Distributed post by high-throughput subscribes to message system and MySQL the two components, realizes the uniformity of database and queue
Method.
Fig. 1 is Processes Tag method flow diagram provided in an embodiment of the present invention.Processes Tag provided in an embodiment of the present invention
Method is comprised the following steps that：
Step S101, the solicited message of remote procedure call protocol write in First ray.
In the present embodiment, First ray can be specifically head write-in queue, and the second sequence can be specifically transaction queues.
Remote procedure call protocol uses Client/Server pattern.Requestor is exactly a client computer, and service providing program is just
It is a server.First, client calls process sends a recalls information for having a process parameter to service processes, then etc.
Information to be answered.In server end, process keeps sleep state untill recalls information is reached.When a recalls information is arrived
Reach, server obtains process parameter, result of calculation sends reply message, then waits next recalls information, finally, client
Hold calling process to receive reply message, obtain proceeding results, then call execution to proceed.
In the present embodiment, the solicited message write head of remote procedure call protocol can be write in queue, if this
Individual message just writes failure, directly returns an error to called side, allows it to retry.
Step S102, processing data storehouse affairs.
If step S103, db transaction fail, the offset coordinates of the First ray, the offset coordinates are moved
For identifying, the solicited message is processed to be finished.
If db transaction fails, slip-on head writes the offset coordinates of queue, represents this request and has been dealt with
Finish.
If the success of step S104, db transaction, the solicited message is write in the second sequence.
If db transaction success, following this program of write-in transaction queues.
If step S105, the solicited message are successfully written in second sequence, the First ray is moved
Offset coordinates.
If writing queue success, slip-on head writes the offset coordinates of queue, represents this request and be processed.
In addition, if write-in queue failure, returns successfully to called side, it is then asynchronous to go to retry transaction queues this program of writing.
Message is successfully arrived in db transaction to be written in the middle of transaction queues this programs, head writes the offset coordinates of queue
All do not moved, that is, if this process is interrupted, can from the beginning write queue and be restored back to.By retrying,
Final transaction queues write successfully.This when, slip-on head write the offset coordinates of queue, marked this request is processed to finish.
Above procedure is complete to mark by introducing head write-in queue and controlling the offset coordinate position of this program
Distributed transaction whether have been dealt with into.This method affairs different from the past using database weigh this as standard
It is individual to handle the method whether completed.Demand without rollback in this process, as long as database writes successfully, message queue is write
Entering will succeed anyway.The key of whole scheme be by head write queue write-in and offset coordinates movement the two
Action, marked the scope of a distributed transaction.As long as this process is not finished completely, it will be write by constantly retrying head
The mode of enqueue ensures that it is eventually completely performed.
The embodiment of the present invention is by being applied to queue technology the micro services collection of pure remote procedure call protocol sync
In group, the degree of accuracy of remote procedure call protocol and the service message of asynchronous queue is improved.
The Processes Tag method flow diagram that Fig. 2 provides for another embodiment of the present invention.On the basis of above-described embodiment, this
The Processes Tag method that inventive embodiments are provided is comprised the following steps that：
Step S201, each remote procedure call protocol thread of mark, each remote procedure call protocol thread correspondence one
Individual offset coordinates, the offset coordinates are used to identify whether the remote procedure call protocol thread runs succeeded.
If step S202, the first remote procedure call protocol thread are before the second remote procedure call protocol thread, institute
State the second remote procedure call protocol thread to be successfully executed, the first remote procedure call protocol thread is not performed,
The offset coordinates are not moved then.
If step S203, the first remote procedure call protocol thread are before the second remote procedure call protocol thread, institute
State the first remote procedure call protocol thread to be successfully executed, the second remote procedure call protocol thread is not performed,
Then move the offset coordinates.
If important service logic is hung over behind message queue.It has to be ensured that data in message queue is complete
Whole property, it is impossible to have the situation of loss.So can not be the logic using the write-in of message queue as a bypass, but should be
Message queue is put into main flow.If message queue write-in failure or time-out, mistake all should be directly returned to, rather than permit
Permitted to continue executing with.
The distributed post that this local queue is encapsulated into a high-throughput is subscribed to message system by us in this programme
The agency of system is used as the agency being written locally, that is to say, that introduce local queue as revealing all the details.The distributed post of high-throughput
The need for the stability and delay for subscribing to message system can not meet online service often.If for example, reliably to write three
Copy, the distributed post of high-throughput, which subscribes to message system, to be needed to wait the response of multiple middlewares, and this delay may
Have than larger fluctuation.In situation about can not write in time, thus we need to use set forth herein local file reveal all the details
Mode serves as a buffering, and an availability is constituted indeed through the queue of local file queue combination remote distributed is introduced
It is higher, postpone lower combination queue scheme.
When no head writes queue, remote procedure call protocol implementation procedure is as follows：Series process, because not having
Protection, it is possible that being interrupted, it is impossible to be ensured that complete execution.The purpose for introducing head write-in queue is exactly to allow this process to become
Reliably.
Assuming that being whole processing procedure, the function for the distributed post subscription message system of a high-throughput is only
Account for, this also implies that the concurrent processing thread (or association's journey) of how many remote procedure call protocol requires how many
Individual corresponding function corresponds to the processing state of thread to track.It can thus become very uneconomical, it is necessary to substantial amounts of high-throughput
Distributed post subscribe to message system function.But if allow multiple remote procedure call protocol threads to share one high handle up
The distributed post of amount subscribes to message system function and goes to coordinate multiple remote procedure calls, it is necessary to newly increase an administrator unit
The movement of the coordinate of agreement thread simultaneously marks running succeeded for affairs.Detailed process is as follows：
Remote procedure call protocol thread 1, is written with A1 (head write-in daily record), and its offset coordinates is 1.
Remote procedure call protocol thread 2, is written with A2, and its offset coordinates is 2.
Remote procedure call protocol thread 3, is written with A3, and its offset coordinates is 3.
Remote procedure call protocol thread 3 is finished, and is intended to that A3 is labeled as to run succeeded, mobile offset coordinates to 3.But
It is, because of above 1 and 2, to be also not carried out success, this when, offset coordinates can not be moved.
Remote procedure call protocol thread 1 is finished, and is intended to that A1 is labeled as to run succeeded, mobile offset coordinates to 1.Cause
Not have not carried out the A of completion above, so this when of offset coordinates are moved to 1 success.
Remote procedure call protocol thread 2 is finished, and is intended to that A2 is labeled as to run succeeded, mobile offset coordinates to 2.Cause
Have been carried out being over for 3 below, so offset coordinates are updated directly as 3.
Step S204, the solicited message of remote procedure call protocol write in First ray.
Step S205, processing data storehouse affairs.
If step S206, db transaction fail, the offset coordinates of the First ray, the offset coordinates are moved
For identifying, the solicited message is processed to be finished.
If the success of step S207, db transaction, the solicited message is write in the second sequence.
If step S208, the solicited message are successfully written in second sequence, the First ray is moved
Offset coordinates.
The embodiment of the present invention is by being applied to queue technology the micro services collection of pure remote procedure call protocol sync
In group, the degree of accuracy of remote procedure call protocol and the service message of asynchronous queue is improved.
Fig. 3 is the structure chart of Processes Tag device provided in an embodiment of the present invention.Process mark provided in an embodiment of the present invention
The handling process that device can be provided with executive process labeling method embodiment is remembered, as shown in figure 3, Processes Tag device 30 includes：
Writing module 31, processing module 32, mobile module 33, wherein, writing module 31 is used for the request of remote procedure call protocol
In information write-in First ray；Processing module 32 is used for processing data storehouse affairs；Mobile module 33 is used for when db transaction loses
When losing, the offset coordinates of the mobile First ray, for identifying, the solicited message is processed to be finished the offset coordinates；
If db transaction success, writing module 31 writes the solicited message in the second sequence；If the solicited message
It is successfully written in second sequence, then mobile module 33 moves the offset coordinates of the First ray.
The embodiment of the present invention is by being applied to queue technology the micro services collection of pure remote procedure call protocol sync
In group, the degree of accuracy of remote procedure call protocol and the service message of asynchronous queue is improved.
The structure chart for the Processes Tag device that Fig. 4 provides for another embodiment of the present invention.On the basis of above-described embodiment,
If the solicited message is not successfully written in second sequence, writing module 31 again writes the solicited message
In second sequence.
Further, Processes Tag device 30 also includes：Mark module 34, mark module 34 is used to mark each long-range mistake
Journey invocation protocol thread, one offset coordinates of each remote procedure call protocol thread correspondence, the offset coordinates are used to identify
Whether the remote procedure call protocol thread runs succeeded.
If the first remote procedure call protocol thread is before the second remote procedure call protocol thread, described second is long-range
Invocation of procedure agreement thread is successfully executed, and the first remote procedure call protocol thread is not performed, then mobile module
33 do not move the offset coordinates.
If the first remote procedure call protocol thread is before the second remote procedure call protocol thread, described first is long-range
Invocation of procedure agreement thread is successfully executed, and the second remote procedure call protocol thread is not performed, then mobile module
The 33 movement offset coordinates.
The method that Processes Tag device provided in an embodiment of the present invention can be provided specifically for performing above-mentioned Fig. 1 is implemented
Example, here is omitted for concrete function.
The embodiment of the present invention is by being applied to queue technology the micro services collection of pure remote procedure call protocol sync
In group, the degree of accuracy of remote procedure call protocol and the service message of asynchronous queue is improved.
In summary, queue technology by being applied to pure remote procedure call protocol sync by the embodiment of the present invention
In micro services cluster, the degree of accuracy of remote procedure call protocol and the service message of asynchronous queue is improved.
, can be by it in several embodiments provided by the present invention, it should be understood that disclosed apparatus and method
Its mode is realized.For example, device embodiment described above is only schematical, for example, the division of the unit, only
Only a kind of division of logic function, can there is other dividing mode when actually realizing, such as multiple units or component can be tied
Another system is closed or is desirably integrated into, or some features can be ignored, or do not perform.It is another, it is shown or discussed
Coupling each other or direct-coupling or communication connection can be the INDIRECT COUPLINGs or logical of device or unit by some interfaces
Letter connection, can be electrical, machinery or other forms.
The unit illustrated as separating component can be or may not be it is physically separate, it is aobvious as unit
The part shown can be or may not be physical location, you can with positioned at a place, or can also be distributed to multiple
On NE.Some or all of unit therein can be selected to realize the mesh of this embodiment scheme according to the actual needs
's.
In addition, each functional unit in each embodiment of the invention can be integrated in a processing unit, can also
That unit is individually physically present, can also two or more units it is integrated in a unit.Above-mentioned integrated list
Member can both be realized in the form of hardware, it would however also be possible to employ hardware adds the form of SFU software functional unit to realize.
The above-mentioned integrated unit realized in the form of SFU software functional unit, can be stored in an embodied on computer readable and deposit
In storage media.Above-mentioned SFU software functional unit is stored in a storage medium, including some instructions are to cause a computer
Equipment (can be personal computer, server, or network equipment etc.) or processor (processor) perform the present invention each
The part steps of embodiment methods described.And foregoing storage medium includes：USB flash disk, mobile hard disk, read-only storage (Read-
Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disc or CD etc. it is various
Can be with the medium of store program codes.
Those skilled in the art can be understood that, for convenience and simplicity of description, only with above-mentioned each functional module
Division progress for example, in practical application, can distribute complete by different functional modules by above-mentioned functions as needed
Into the internal structure of device being divided into different functional modules, to complete all or part of function described above.On
The specific work process of the device of description is stated, the corresponding process in preceding method embodiment is may be referred to, will not be repeated here.
Finally it should be noted that：Various embodiments above is merely illustrative of the technical solution of the present invention, rather than its limitations；To the greatest extent
The present invention is described in detail with reference to foregoing embodiments for pipe, it will be understood by those within the art that：Its according to
The technical scheme described in foregoing embodiments can so be modified, or which part or all technical characteristic are entered
Row equivalent substitution；And these modifications or replacement, the essence of appropriate technical solution is departed from various embodiments of the present invention technology
The scope of scheme.
Claims (10)
1. a kind of Processes Tag method, it is characterised in that including：
By in the solicited message write-in First ray of remote procedure call protocol；
Processing data storehouse affairs；
If db transaction fails, the offset coordinates of the First ray are moved, the offset coordinates are described for identifying
Solicited message is processed and finished；
If db transaction success, the solicited message is write in the second sequence；
If the solicited message is successfully written in second sequence, the offset coordinates of the First ray are moved.
2. according to the method described in claim 1, it is characterised in that if the solicited message is not successfully written described second
In sequence, then the solicited message is write in the second sequence again.
3. method according to claim 1 or 2, it is characterised in that the solicited message by remote procedure call protocol
Before writing in First ray, in addition to：
Mark each remote procedure call protocol thread, one offset coordinates of each remote procedure call protocol thread correspondence, institute
Stating offset coordinates is used to identify whether the remote procedure call protocol thread runs succeeded.
4. method according to claim 3, it is characterised in that if the first remote procedure call protocol thread is long-range second
Before invocation of procedure agreement thread, the second remote procedure call protocol thread is successfully executed, first remote process
Invocation protocol thread is not performed, then does not move the offset coordinates.
5. method according to claim 3, it is characterised in that if the first remote procedure call protocol thread is long-range second
Before invocation of procedure agreement thread, the first remote procedure call protocol thread is successfully executed, second remote process
Invocation protocol thread is not performed, then moves the offset coordinates.
6. a kind of Processes Tag device, it is characterised in that including：
Writing module, for the solicited message of remote procedure call protocol to be write in First ray；
Processing module, for processing data storehouse affairs；
Mobile module, for when db transaction fails, the offset coordinates of the mobile First ray, the offset coordinates to be used
In identifying, the solicited message is processed to be finished；
If db transaction success, said write module writes the solicited message in the second sequence；
If the solicited message is successfully written in second sequence, the mobile module moves the inclined of the First ray
Move coordinate.
7. Processes Tag device according to claim 6, it is characterised in that if the solicited message is not successfully written
In second sequence, then said write module again writes the solicited message in the second sequence.
8. the Processes Tag device according to claim 6 or 7, it is characterised in that also include：
Mark module, for marking each remote procedure call protocol thread, each remote procedure call protocol thread correspondence one
Individual offset coordinates, the offset coordinates are used to identify whether the remote procedure call protocol thread runs succeeded.
9. Processes Tag device according to claim 8, it is characterised in that if the first remote procedure call protocol thread exists
Before second remote procedure call protocol thread, the second remote procedure call protocol thread is successfully executed, and described first
Remote procedure call protocol thread is not performed, then the mobile module does not move the offset coordinates.
10. Processes Tag device according to claim 8, it is characterised in that if the first remote procedure call protocol thread
Before the second remote procedure call protocol thread, the first remote procedure call protocol thread is successfully executed, and described
Two remote procedure call protocol threads are not performed, then the mobile module moves the offset coordinates.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710501482.2A CN107277022B (en) | 2017-06-27 | 2017-06-27 | Process marking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710501482.2A CN107277022B (en) | 2017-06-27 | 2017-06-27 | Process marking method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107277022A true CN107277022A (en) | 2017-10-20 |
| CN107277022B CN107277022B (en) | 2020-03-13 |
Family
ID=60069666
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710501482.2A Active CN107277022B (en) | 2017-06-27 | 2017-06-27 | Process marking method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107277022B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108415736A (en) * | 2018-02-06 | 2018-08-17 | 新浪网技术(中国)有限公司 | The method, apparatus and equipment of program process are marked using process filesystem |
| CN109725944A (en) * | 2018-12-29 | 2019-05-07 | 北京三快在线科技有限公司 | Remote procedure calling (PRC) method and device, electronic equipment, storage medium |
| CN110532066A (en) * | 2018-05-23 | 2019-12-03 | 中国移动通信集团浙江有限公司 | A kind of realization method and system of transaction consistency |
| CN110659141A (en) * | 2018-06-30 | 2020-01-07 | 武汉斗鱼网络科技有限公司 | Instruction execution method and related equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1725186A (en) * | 2004-07-23 | 2006-01-25 | 中兴通讯股份有限公司 | Multiple data base data syne method |
| US20070185937A1 (en) * | 2005-12-19 | 2007-08-09 | Anand Prahlad | Destination systems and methods for performing data replication |
| CN101097527A (en) * | 2006-06-27 | 2008-01-02 | 中国银联股份有限公司 | Flowpath scheduling method and system of application progress |
| CN102023974A (en) * | 2009-09-14 | 2011-04-20 | 中国移动通信集团公司 | Method, device and system for processing message by message queue |
| US8185622B2 (en) * | 2007-10-16 | 2012-05-22 | Ricoh Company, Ltd. | Condition dependent data maintenance system for a plurality of functional entities |
| CN105095364A (en) * | 2015-06-26 | 2015-11-25 | 车智互联（北京）科技有限公司 | Data synchronizing system and method |
| CN105956166A (en) * | 2016-05-19 | 2016-09-21 | 北京京东尚科信息技术有限公司 | Database reading-writing method and database reading-writing apparatus |
-
2017
- 2017-06-27 CN CN201710501482.2A patent/CN107277022B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1725186A (en) * | 2004-07-23 | 2006-01-25 | 中兴通讯股份有限公司 | Multiple data base data syne method |
| US20070185937A1 (en) * | 2005-12-19 | 2007-08-09 | Anand Prahlad | Destination systems and methods for performing data replication |
| CN101097527A (en) * | 2006-06-27 | 2008-01-02 | 中国银联股份有限公司 | Flowpath scheduling method and system of application progress |
| US8185622B2 (en) * | 2007-10-16 | 2012-05-22 | Ricoh Company, Ltd. | Condition dependent data maintenance system for a plurality of functional entities |
| CN102023974A (en) * | 2009-09-14 | 2011-04-20 | 中国移动通信集团公司 | Method, device and system for processing message by message queue |
| CN105095364A (en) * | 2015-06-26 | 2015-11-25 | 车智互联（北京）科技有限公司 | Data synchronizing system and method |
| CN105956166A (en) * | 2016-05-19 | 2016-09-21 | 北京京东尚科信息技术有限公司 | Database reading-writing method and database reading-writing apparatus |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108415736A (en) * | 2018-02-06 | 2018-08-17 | 新浪网技术(中国)有限公司 | The method, apparatus and equipment of program process are marked using process filesystem |
| CN108415736B (en) * | 2018-02-06 | 2021-03-30 | 新浪网技术(中国)有限公司 | Method, device and equipment for marking program process by using process file system |
| CN110532066A (en) * | 2018-05-23 | 2019-12-03 | 中国移动通信集团浙江有限公司 | A kind of realization method and system of transaction consistency |
| CN110659141A (en) * | 2018-06-30 | 2020-01-07 | 武汉斗鱼网络科技有限公司 | Instruction execution method and related equipment |
| CN110659141B (en) * | 2018-06-30 | 2022-01-04 | 武汉斗鱼网络科技有限公司 | Instruction execution method and related equipment |
| CN109725944A (en) * | 2018-12-29 | 2019-05-07 | 北京三快在线科技有限公司 | Remote procedure calling (PRC) method and device, electronic equipment, storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107277022B (en) | 2020-03-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107277022A (en) | Processes Tag method and device | |
| JP3851272B2 (en) | Stateful program entity workload management | |
| US8849776B2 (en) | Method and system for resolving data inconsistency | |
| KR102072726B1 (en) | Systems and methods for supporting inline delegation of middle-tier transaction logs to database | |
| US9787561B2 (en) | System and method for supporting a selection service in a server environment | |
| CN104601696B (en) | Service processing method, service calling system, device and system | |
| CN105468302B (en) | A kind of method, apparatus and system of processing data | |
| CN107113341B (en) | System for high throughput processing of transactions in a distributed relational database management system for data partitioning | |
| US20130145371A1 (en) | Batch processing of business objects | |
| CN108536532A (en) | A kind of batch tasks processing method and system | |
| US9189303B2 (en) | Shadow queues for recovery of messages | |
| CN102971711A (en) | An apparatus for processing a batched unit of work | |
| CN106254144A (en) | Fault location platform, Fault Locating Method and device | |
| CN108965457A (en) | A kind of message delivery method of distributed cluster system, device, equipment and medium | |
| CN105808414A (en) | Log processing method and log processing electronic equipment | |
| CN111190810B (en) | Method, device, server and storage medium for executing test task | |
| CN108491254A (en) | A kind of dispatching method and device of data warehouse | |
| CN108416657B (en) | Order generation method and equipment based on consultation service | |
| CN105094811B (en) | A kind of method and apparatus of event handling | |
| JP5065259B2 (en) | Apparatus, system, method, and computer program useful for communication between enterprise information system and client (device, system, and method useful for communication between enterprise information system and client) | |
| CN104407820B (en) | Data processing method based on solid hard disk storage system, device and system | |
| CN108897876A (en) | A kind of data cut-in method and device | |
| US20210406102A1 (en) | Method and apparatus for providing asynchronicity to microservice application programming interfaces | |
| JP2009536403A (en) | Work item event processing | |
| CN108965054A (en) | A kind of client and service end data rapid interactive method |
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 |