CN102724304A - Information warehouse federation in subscription/release system and data synchronization method - Google Patents
Information warehouse federation in subscription/release system and data synchronization method Download PDFInfo
- Publication number
- CN102724304A CN102724304A CN2012101845082A CN201210184508A CN102724304A CN 102724304 A CN102724304 A CN 102724304A CN 2012101845082 A CN2012101845082 A CN 2012101845082A CN 201210184508 A CN201210184508 A CN 201210184508A CN 102724304 A CN102724304 A CN 102724304A
- Authority
- CN
- China
- Prior art keywords
- data
- message
- federal
- information warehouse
- information
- 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
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an information warehouse federation in a subscription/release system and a data synchronization method. The information warehouse federation comprises a plurality of information warehouses identical in structure and equal in level. Each information warehouse comprises a data storage module, a synchronous processing module and a public service module. Other information warehouses in the federation can be notified of data in one information warehouse needing to be updated in a message-based manner by means of collaboration among the modules; the other information warehouses correspondingly update after receiving the updating message and return processed results to a message transmission source; and the message transmission source updates the self data after receiving feedback messages. The information warehouse federation and the data synchronization method have the advantages that the data synchronization method which is effective, rapid and easy to implement is provided for synchronization of real-time data among the information warehouses in the subscription/release system low in data size and updating frequency, robustness, stability and fault tolerance of the system are improved, and consistency of the data among the information warehouses forming the federation in the subscription/release system is guaranteed.
Description
Technical field
What the present invention relates to is a kind of computer distributed system, be specifically related to a kind of in the subscription/publication system in the federal and method of between these federal members, carrying out data sync of information warehouse.
Background technology
Information warehouse federal member data sync in the subscription/publication system belongs to data synchronization technology category in the distributed system.Data sync mainly contains following several kinds of simultaneous techniquess in distributed system at present:
1. affairs are controlled method
1.1. traditional affairs control method
In distributed data base system; " affairs " are a series of indivisible sequences of operation; Database is converted to another coherency state from a coherency state,, may causes data trnascription inconsistent because there are concurrent execution in global transaction and local affairs.Traditional affairs control method guarantees the serializability that global transaction and local affairs are carried out through distributed two-phase lock agreement (2PL agreement); Can guarantee the consistency scheduling of affairs, and come to upgrade synchronously each copy data through distributed two-phase commitment protocol (2PC agreement).This record that operation relates to data distributed data base system few, that the affairs retention time is not long is effective.And, user big in some data volumes to the big situation of the opereating specification of data under, the affairs retention time is long, if employing 2PL agreement then can seriously influence the transaction concurrency degree; Can not satisfy actual needs, simultaneously, the method for 2PC agreement or the 3PC agreement traffic on the net is very big; And, therefore, can make the user be absorbed in long insufferable wait state because network speed is limited; Or run into frequent affairs failure, it is too many to restart affairs, causes the application program operational efficiency low.
1.2. extended transactions control method
Under distributed environment; The 2PC agreement is to realize a main principle of affairs atomicity; Yet most of original Database Systems are not supported this agreement; Extended transactions control rule does not rely on local database systems and whether supports the 2PC agreement, but global subgroup affairs and local affairs are expanded, and has introduced lock table and log sheet for each local data bank; It carries out extended transactions on local data bank and control table, they are responsible for safeguarding the recovery of overall serializability and actual transaction.Detect lock through extended transactions, take place to avoid conflict and recover.This method has been safeguarded the autonomy of local affairs on certain basis, the attend to the basic or the fundamental execution efficient of body that reducing but it has increased the burden of affairs gets over.
2. duplication control method
2.1. synchronization replication control method
Utilize synchronization replication to make each data trnascription keep tight consistency, promptly the value of the copy of different websites of any moment is always consistent.Like this; The global transaction management system is wanted the website at each copy place of explicit data; When affairs had been carried out renewal to a certain data trnascription, the global transaction management system must be consistent with each copy of maintenance data to the message of other websites transmission force users modification data trnascriptions.But, then must wait for after it recovers and duplicating again, so data are not strict conformance for the website that breaks down.Because frequent to the updating data operation, thereby also frequent to the copy message of system's transmission, the system communication amount is big, has reduced system handles speed.And for a lot of Database Systems, the data consistent that it is not strict allows the data that the access time relatively lags behind as spatial database, adopts synchronization replication control and impracticable.
2.2. asynchronous replication control method
Utilize asynchronous replication to make each data trnascription keep loose consistency, i.e. the modification made of updating data and its each copy is duplicated for some time at interval, and at a time the value of the copy of different websites possibly be inconsistent, and data are temporarily asynchronous.It mainly solves two problems, and promptly how to capture to Update Information and when duplicate.The general employing based on the transaction journal method with based on trigger method capture system upgraded operation, and most of Database Systems generally adopt transaction journal to catch Data Update, like Sybase, and Informix, Microsoft SQL Server etc.But because the transaction journal form maybe be inequality, it is quite difficult to design the general database journal fetch program, thereby some systems adopt trigger methods.For the trigger method,, can trigger dependent event the content of record data source and Data Update takes place in case the object of being followed the tracks of is updated.Update Information for what the device that is triggered was caught, by replication server each copy is upgraded, replication server need guarantee that the data that are replicated are last renewal results.
3. message queue method
Message queue is a kind of mechanism of interprocess communication; Come exchange message through visiting shared system message queue between two or more processes; Here with the conceptual expansion of message queue to the interprocess communication between the different websites that are positioned under the distributed environment; Realize that by message management mechanism reliable message transmits on Internet, the message queue that wherein relates to has transmit queue, receives formation, replys formation and administration queue.Application program is stored in the address of lastest imformation and local echoing formation and administration queue in the message after accomplishing Data Update on the local data base, sends in the far-end reception formation; Message gives that at first to get into local transmit queue etc. after the message management mechanism to be sent, and normal like all, the far-end that message will be delivered to the application program appointment receives in the formation; Simultaneously, a background process program is being kept watch on the reception formation of oneself always, in case there is message to arrive; It will read message; And local data base implemented the renewal operation described in the message, if upgrade Chen Min etc.: Method of data consistency maintenance research success in the distributed data base system, then processing end; Otherwise send error messages according to the address information of replying formation; Another background process program is replied formation in supervision always, and according to the error message of receiving, it will attempt to cancel corresponding renewal operation in local data base.This method provides asynchronous refresh between database, rather than upgrades synchronously, and what possibly read like this is not latest data, so it is not suitable for the distributed data base system that requires real time data synchronous.
Summary of the invention
The object of the present invention is to provide in the subscription/publication system of a kind of robustness that can improve distributed system, stability information warehouse federal.The present invention also aims to provide a kind of and can avoid dirty data reading, improve the federal method of data synchronization of information warehouse in the subscription/publication system of fault-tolerance.
The objective of the invention is to realize like this:
The federal member of information warehouse federation and sane level identical by a plurality of structures in the subscription/publication of the present invention system, be that information warehouse constitutes, the structure of each information warehouse is following:
(1) data memory module, the basic module of the persistent storage of responsible data, the data of storage are divided into two kinds of federal data, business datums, and federal data are state, the positional information of each federal member; Business datum is that publish/subscribe system moves necessary business datum;
(2) synchronous processing module, the module of data is divided into message queue, monitor, trigger, controller four sub-module between the responsible synchronous federal member; Message queue is used for the request that writes that the buffer memory application program is sent; Monitor is used for the surveillance state and pushes to other module; Trigger is used for according to the condition trigger action; Controller is used to control whole simultaneous operation process;
(3) public service module is responsible for providing to upper layer module the bottom module of public service, is divided into time management, federal condition managing, bottom communication three sub-module; Time management is used for each federal member is carried out time synchronized; Federal condition managing is used to safeguard state, positional information between the federal member; The bottom communication is used for the transmitting-receiving of realization system data.
Said data memory module adopts database or the storage of XML file mode.
The federal method of data synchronization of information warehouse comprises the steps: in the subscription/publication system
(1) application program in the system is initiated " writing message " to a certain information warehouse A;
(2) information warehouse A will " write message " and deposit message queue, triggering synchronous operation in;
(3) information warehouse A takes out in the message queue and descends a piece of news most, selects a certain federal member to send synchronization message with the message packing and according to federal state;
(4) information warehouse A sends after the message, picks up counting, if do not receive that the other side replys within a certain period of time, then retransmits this message, replys as if receiving, then gets into for (8) step;
Whether (5) information warehouse B receives synchronization message, judge self to have than this synchronization message and initiate more Zao synchronous initiation message end as yet of time, if having, then abandons the synchronization message of information warehouse A, if do not have, then receives synchronization message and begins to carry out simultaneous operation;
(6) resolve the synchronization message of receiving, according to the retrieval of the major key in the message content self existing business data;
(7) according to self existing business data cases, how judgement operates the own service data;
(8) information warehouse B accomplishes after the operation to the own service data, and to information warehouse A transmit operation success response, this moment, information warehouse B accomplished synchronously;
(9) information warehouse A receive operate successfully corresponding after, select next federal member to send synchronization message according to federal state, if do not had next federal member this moment, then begin to carry out self simultaneous operation, upgrade the own service data;
(10) information warehouse A accomplishes after the service data manipulating to self, federal in all federal member data synchronous, the message that has been performed of next bar in the information warehouse A deletion message queue is accomplished synchronously.
The method of data synchronization that the present invention proposes forces the linear in order synchronizing process of carrying out of all federal members in the federation with simple structure and less network resource consumption; Avoid many federal members to initiate the synchronous data that cause mutually and repeated problems such as rewriting, dirty data reading, effectively improved robustness, stability, the fault-tolerance of system.The present invention also has following three characteristics in addition.
The first, the complete equality in the status of each federal member in federation among the present invention, synchronizing process are accomplished through the controller control of federal member self fully, and do not need a special node to participate in.The realization of this federation is provided convenience, and has also made things convenient for the user to dispose federal environment simultaneously.In synchronizing process, synchronous message need not passed through certain specific node transfer, and offered load is balance comparatively, the system bottleneck of having avoided specific nodes network service to cause greatly.
The second, federal as a logical construction among the present invention, application programs is transparent fully, and application program is directly visited, operated remains information warehouse itself, and the state of federation is maintained mutually by information warehouse each other.This brings great convenience for the exploitation of application program and deployment, and the developer does not even need application programs to carry out any modification, just can let it operate under the federal environment of information warehouse.
The 3rd, information warehouse inside does not need the extra backup of storage service data among the present invention, and the message that writes of application program initiation was getting into the message queue buffer memory before synchronously, treat to store in the business datum more afterwards synchronously.This has simplified information warehouse as far as possible under the prerequisite that guarantees to be accomplished synchronously structure, making it can use more resources to accomplish to application program provides storage, writes the one's work of service, the generation of also fundamentally having stopped dirty data reading.
Description of drawings
Fig. 1 is that federal interior federal member is the functional structure chart of information warehouse.
Fig. 2 is that synchronous program flow diagram is initiated synchronously, received to federal interior federal member.
Fig. 3 is a flow chart of accomplishing a data synchronization process instance between the federal member.
Embodiment
Below in conjunction with accompanying drawing and embodiment the present invention is further specified.
Technical thought of the present invention is: in not influencing the subscription/publication system under the prerequisite of application program, seek a kind of simple in structure, network bandwidth and take between the information warehouse little, that the engineering exploitativeness is strong the technology of synchrodata in real time.This technology can be to the characteristics of subscription/publication system; The module information warehouse is federal; The synchronization request that forces a plurality of federal members in federation serial is in order carried out, and guarantees that with this federal synchronizing process correctly accomplishes, and improves robustness, stability and the fault-tolerance of whole subscription/publication system.
In conjunction with Fig. 1, the structure in federal (100) internal information warehouse of information warehouse (102) comprises following components in the subscription/publication of the present invention system:
(1) data memory module (104).
Data memory module is the basic module that information warehouse is deposited information, data.The main persistent storage of being responsible for data according to the difference and the running environment of subscription/publication system, can adopt methods such as database, XML file to carry out the structural data storage, for application access in the system.The data of storing in the data memory module are divided following two types.
1. federal data (106): the information warehouse in the system adds federal as federal member, federal data are information such as each federal member state, position in the federation, with the mode persistent storage of bivariate table for mutual access between the federal member.
2. business datum (108): deposit the business datum that application program produces, uses in the subscription/publication system, what need be synchronized is this partial data.Topic in the DDS system etc. for example.
(2) synchronous processing module (110)
Synchronous processing module mainly is responsible for the data sync task between the federal member (information warehouse) in the federation.Constitute by following four sub-module.
1. message queue (112): " writing " request that client application is initiated to information warehouse in the subscription/publication system does not directly deposit in the data memory module, carries out buffer memory in the message queue but temporarily get into, for Synchronous Processing.
2. monitor (114): the message in monitor message warehouse internal state and the network, and to the module PUSH message of needs.
3. trigger (116): receive the message that monitor pushes, when reaching trigger condition, trigger action.For example, when in the message queue message being arranged, the triggering synchronous operation.
4. controller (118): whole simultaneous operation process is controlled, to guarantee correct synchronously the completion.
(3) public service module (120)
Public service module is the service module of system bottom, for upper layer data memory module and synchronous processing module provide the time synchronized service, safeguard functions such as federal member state information, correspondence with foreign country.
1. time management (122): realize federal interior each federal member time synchronized, and interface is provided, so that obtain current simulation time at any time.
2. federal condition managing (124): outwards broadcast heartbeat data and receive the other side's heartbeat data, to safeguard federal interior all member conditions, positional information.
3. bottom communication (126): the bottom communication platform, be responsible in system, sending, receiving data.
More than three big modules constituted a complete information warehouse.When having only an information warehouse in the whole publish/subscribe system, can think that this information warehouse forms a federation that only comprises a federal member.And after a plurality of information warehouses were formed federation, the data between all federal members need be carried out synchronously, and according to the state of information warehouse, whole federation can be divided into following three states:
(1) coherency state
Each federal member, i.e. data consistent in the information warehouse (102) in this moment federation.
(2) accumulated state
This moment federation in each federal member; Be possibly temporarily can't communicate by letter for some reason between the information warehouse (102), the client application in the subscription/publication system accumulates in the message queue (112) of information warehouse " writing " request of the information warehouse that connected separately.Though the business datum (108) that store in each information warehouse this moment still is consistent, the message of accumulation need be synchronized.
(3) Synchronous Processing state
In case certain federal member in federal, promptly the message queue (112) of information warehouse (102) has accumulation, then gets into the Synchronous Processing state immediately.Accomplish after all simultaneous operation, system returns coherency state.
Whole federation is constantly circulation under these three states, and a data sync operation is all accomplished in circulation each time.
As shown in Figure 2, among the present invention federal between the federal member process of data sync comprise following step:
1. the application program in the system is initiated " writing message " (202) to a certain information warehouse A, and this moment, the coherency state of whole federation finished, and got into accumulated state.
2. information warehouse A will " write message " and deposit message queue (204) in.Using message queue (108) is in order " to write message " carrying out buffer memory in the process synchronously, to force these " to write message " and in federation, carry out in order not influencing simultaneously the reading and writing data service that information warehouse itself provides to application program again synchronously.
3. the monitor (114) among the information warehouse A listens to message queue (108) not for empty, the operation of trigger (116) triggering synchronous, and information warehouse A will be self-marked as " not synchronous regime " (206).Being labeled as " not synchronous regime " is in order according to circumstances to abandon other federal member to the request synchronization message of self initiating in the implementation synchronously.This moment, the accumulated state of whole federation finished, and got into the Synchronous Processing state.
4. the controller (118) among the information warehouse A takes out in the message queue (108) next bar data (may exist multiple messages in message queue, to accumulate), with message packing (206).Package information comprises formation numbering (whole system this value in service is unique), timestamp (current system emulation time), message content (concrete operations that needs are carried out).
5. according to federal status data (208), in order, at first send and be somebody's turn to do " request synchronization message " to another federal member information warehouse B, and pick up counting (216).
5.1. if do not receive at the appointed time that information warehouse B is to this subsynchronous " operation success message "; Possibly be because information warehouse B does not receive " request synchronization message ", also might be because " the operation success message " that information warehouse B sends successfully do not arrive (218).No matter which kind of reason all repeated for the 5th step.
5.2. if receive at the appointed time that information warehouse B to this subsynchronous " operation success message ", jumped to for the 10th step (218).
6. the monitor (114) among the information warehouse B listens to " request synchronization message " (224) in the network.
7. the controller (118) among the information warehouse B obtains message and unpacks, and time for reading is stabbed (226).
7.1., then accept synchronously if oneself state is " synchronous regime ", will be self-marked as " not synchronous regime ", got into for the 8th step (228).
7.2., compare a timestamp (228) in " the request synchronization message " of self outwards sending if oneself state is " a not synchronous regime ".It is the situation such as deadlock of to send " request synchronization message " simultaneously, mutually between two information warehouses and causing in order to solve that joining day is stabbed purpose relatively.
7.2.1., then interrupt self initiate synchronous if receive the timestamp the when timestamp of message sends synchronization request early than self, accept the synchronization request of receiving, will be self-marked as " not synchronous regime ", got into for the 8th step (230).
7.2.2. be later than the timestamp when self sending synchronization request if receive the timestamp of message, then abandon the other side's synchronization request, proceed the synchronizing process of self initiating (238).
8. information warehouse B formally accepts the other side's synchronization request, and controller (118) unpacks formation numbering, the message content in " request synchronization message ", according to message content, business datum is operated (230).Message is done to judge in order when receiving late " request synchronization message ", to carry out correct handling.
8.1 if message request is for writing, according to major key retrieving information warehouse B available data (232).
8.1.1 if do not have, then write data, got into for the 9th step (234).
8.1.2 if existing, then do not do write operation, got into for the 9th step (234).
8.2 if message request is for deletion, according to major key retrieving information warehouse B available data (232).
8.2.1 if do not have, then do not do deletion action, got into for the 9th step (234).
8.2.2 if existing, then deleted data got into for the 9th step (234).
8.3 if message request is modification, the direct modification data got into for the 9th step (234).
9. to synchronization request transmit leg return success message, comprise former message queue numbering in the message, and oneself state is set to " synchronous regime " (236).
10. the monitor (114) among the information warehouse A listens to " the operation success message " that returns in the network, checks federal status data (208).
10.1. if next federal member is arranged, then initiate (216) synchronously to next federal member information warehouse C, this moment is identical with B to the synchronizing process of information warehouse C, no longer repeats.
10.2. if there is not next federal member, then carry out the own service data manipulation, got into for the 11st step (212).
11. information warehouse A obtains the formation number value in " the operation success message " that returns, and numbers compare (214) with the formation of sending before self.
11.1. as if identical, then upgrade the business datum of self, got into for the 12nd step (214).
11.2., then abandon these " operation success message " (214) if different or this moment, state was " synchronous regime ".
After 12. information warehouse A Updates Information, the deletion corresponding message (214) that has been synchronized of next bar from message queue (112).
13. information warehouse A oneself state is set to " synchronous regime ", this moment, the Synchronous Processing state of whole federation finished, and got into coherency state (220) again.
So far, whole federation carries out the transition to accumulated state from coherency state, gets back to coherency state through the Synchronous Processing state again, and whole federal state is accomplished once circulation, and the data between the federal member have also been passed through the once time synchronization process.
Fig. 3 has provided an instance, this case description between the federation that forms by three information warehouses, from being initiated to the process of accomplishing once time synchronization.Some common abnormal situation have wherein been comprised.
Should be understood that; Concerning the those of ordinary skill in field, the present invention technology place; Can be equal to accordingly according to technical scheme of the present invention and design thereof and change or replacement, and all these changes or replacement, all should belong to the protection range of accompanying claims of the present invention.
Claims (3)
1. information warehouse is federal in the subscription/publication system, the federal member of and sane level identical by a plurality of structures, is that information warehouse constitutes, and it is characterized in that the structure of each information warehouse is following:
(1) data memory module, the basic module of the persistent storage of responsible data, the data of storage are divided into two kinds of federal data, business datums, and federal data are state, the positional information of each federal member; Business datum is that publish/subscribe system moves necessary business datum;
(2) synchronous processing module, the module of data is divided into message queue, monitor, trigger, controller four sub-module between the responsible synchronous federal member; Message queue is used for the request that writes that the buffer memory application program is sent; Monitor is used for the surveillance state and pushes to other module; Trigger is used for according to the condition trigger action; Controller is used to control whole simultaneous operation process;
(3) public service module is responsible for providing to upper layer module the bottom module of public service, is divided into time management, federal condition managing, bottom communication three sub-module; Time management is used for each federal member is carried out time synchronized; Federal condition managing is used to safeguard state, positional information between the federal member; The bottom communication is used for the transmitting-receiving of realization system data.
2. information warehouse is federal in the subscription/publication according to claim 1 system, it is characterized in that said data memory module adopts database or the storage of XML file mode.
3. the federal method of data synchronization of information warehouse in the described subscription/publication of claim 1 system is characterized in that comprising the steps:
(1) application program in the system is initiated " writing message " to a certain information warehouse A;
(2) information warehouse A will " write message " and deposit message queue, triggering synchronous operation in;
(3) information warehouse A takes out in the message queue and descends a piece of news most, selects a certain federal member to send synchronization message with the message packing and according to federal state;
(4) information warehouse A sends after the message, picks up counting, if do not receive that the other side replys within a certain period of time, then retransmits this message, replys as if receiving, then gets into for (8) step;
Whether (5) information warehouse B receives synchronization message, judge self to have than this synchronization message and initiate more Zao synchronous initiation message end as yet of time, if having, then abandons the synchronization message of information warehouse A, if do not have, then receives synchronization message and begins to carry out simultaneous operation;
(6) resolve the synchronization message of receiving, according to the retrieval of the major key in the message content self existing business data;
(7) according to self existing business data cases, how judgement operates the own service data;
(8) information warehouse B accomplishes after the operation to the own service data, and to information warehouse A transmit operation success response, this moment, information warehouse B accomplished synchronously;
(9) information warehouse A receive operate successfully corresponding after, select next federal member to send synchronization message according to federal state, if do not had next federal member this moment, then begin to carry out self simultaneous operation, upgrade the own service data;
(10) information warehouse A accomplishes after the service data manipulating to self, federal in all federal member data synchronous, the message that has been performed of next bar in the information warehouse A deletion message queue is accomplished synchronously.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101845082A CN102724304A (en) | 2012-06-06 | 2012-06-06 | Information warehouse federation in subscription/release system and data synchronization method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101845082A CN102724304A (en) | 2012-06-06 | 2012-06-06 | Information warehouse federation in subscription/release system and data synchronization method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102724304A true CN102724304A (en) | 2012-10-10 |
Family
ID=46949965
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012101845082A Pending CN102724304A (en) | 2012-06-06 | 2012-06-06 | Information warehouse federation in subscription/release system and data synchronization method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102724304A (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102984174A (en) * | 2012-12-21 | 2013-03-20 | 北京邮电大学 | Method and system for reliability guarantee in publish-subscribe system |
| CN103617274A (en) * | 2013-12-05 | 2014-03-05 | 用友软件股份有限公司 | Synchronization method and system |
| CN104156798A (en) * | 2014-07-08 | 2014-11-19 | 四川中电启明星信息技术有限公司 | System data real-time push framework adopting enterprise authority source and method |
| CN107122497A (en) * | 2017-05-25 | 2017-09-01 | 北京微影时代科技有限公司 | Data processing method, device, electronic equipment and computer-readable recording medium |
| CN107273440A (en) * | 2017-05-25 | 2017-10-20 | 北京邮电大学 | Computer application, date storage method, micro services and microdata storehouse |
| CN107301196A (en) * | 2017-05-03 | 2017-10-27 | 北京小度信息科技有限公司 | Method of data synchronization, device, equipment and monitoring server |
| US9940342B2 (en) | 2014-09-25 | 2018-04-10 | Red Hat, Inc. | Stability measurement for federation engine |
| CN108370345A (en) * | 2015-10-09 | 2018-08-03 | 萨托里环球有限责任公司 | System and method for storing message data |
| CN109933412A (en) * | 2019-01-28 | 2019-06-25 | 武汉慧联无限科技有限公司 | Distributed transaction processing method based on distributed message middleware |
| CN110719228A (en) * | 2019-08-27 | 2020-01-21 | 中国船舶重工集团公司第七0九研究所 | Large data packet transmission method and device based on real-time data distribution service |
| CN110895547A (en) * | 2019-11-29 | 2020-03-20 | 交通银行股份有限公司 | Multi-source heterogeneous database data synchronization system and method based on DB2 federal characteristics |
| CN111400053A (en) * | 2020-03-17 | 2020-07-10 | 畅捷通信息技术股份有限公司 | Database access system, method, apparatus and computer-readable storage medium |
| CN112052603A (en) * | 2020-09-25 | 2020-12-08 | 中国直升机设计研究所 | Helicopter-based multi-machine collaborative simulation architecture and data interaction method |
| CN112069160A (en) * | 2020-08-31 | 2020-12-11 | 浙江华瑞信息资讯股份有限公司 | CAP (CAP phase error) data based cleaning synchronization method |
| CN113722401A (en) * | 2021-11-04 | 2021-11-30 | 树根互联股份有限公司 | Data caching method and device, computer equipment and readable storage medium |
| CN115022392A (en) * | 2022-06-24 | 2022-09-06 | 浪潮软件集团有限公司 | IOT-oriented distributed publishing and subscribing service method and system |
| CN115208899A (en) * | 2022-06-29 | 2022-10-18 | 安阳师范学院 | Improved P2P mass scientific data synchronization method |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070174236A1 (en) * | 2006-01-20 | 2007-07-26 | Daniel Pagnussat | Technique for supplying a data warehouse whilst ensuring a consistent data view |
| CN102023973A (en) * | 2009-09-14 | 2011-04-20 | 中国移动通信集团公司 | Method, device and system for synchronizing database with application cache server |
-
2012
- 2012-06-06 CN CN2012101845082A patent/CN102724304A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070174236A1 (en) * | 2006-01-20 | 2007-07-26 | Daniel Pagnussat | Technique for supplying a data warehouse whilst ensuring a consistent data view |
| CN102023973A (en) * | 2009-09-14 | 2011-04-20 | 中国移动通信集团公司 | Method, device and system for synchronizing database with application cache server |
Non-Patent Citations (1)
| Title |
|---|
| 李丹: "基于MRB消息队列的分布式数据库同步的研究与实现", 《信息科技辑》 * |
Cited By (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102984174A (en) * | 2012-12-21 | 2013-03-20 | 北京邮电大学 | Method and system for reliability guarantee in publish-subscribe system |
| CN102984174B (en) * | 2012-12-21 | 2016-04-06 | 北京邮电大学 | Reliability guarantee method and system in a kind of distribution subscription system |
| CN103617274A (en) * | 2013-12-05 | 2014-03-05 | 用友软件股份有限公司 | Synchronization method and system |
| CN103617274B (en) * | 2013-12-05 | 2017-04-26 | 用友网络科技股份有限公司 | Synchronization method and system |
| CN104156798A (en) * | 2014-07-08 | 2014-11-19 | 四川中电启明星信息技术有限公司 | System data real-time push framework adopting enterprise authority source and method |
| CN104156798B (en) * | 2014-07-08 | 2017-12-01 | 四川中电启明星信息技术有限公司 | Enterprise authority source system data real time propelling movement method |
| US9940342B2 (en) | 2014-09-25 | 2018-04-10 | Red Hat, Inc. | Stability measurement for federation engine |
| CN108370345A (en) * | 2015-10-09 | 2018-08-03 | 萨托里环球有限责任公司 | System and method for storing message data |
| CN107301196A (en) * | 2017-05-03 | 2017-10-27 | 北京小度信息科技有限公司 | Method of data synchronization, device, equipment and monitoring server |
| CN107122497A (en) * | 2017-05-25 | 2017-09-01 | 北京微影时代科技有限公司 | Data processing method, device, electronic equipment and computer-readable recording medium |
| CN107273440A (en) * | 2017-05-25 | 2017-10-20 | 北京邮电大学 | Computer application, date storage method, micro services and microdata storehouse |
| CN109933412A (en) * | 2019-01-28 | 2019-06-25 | 武汉慧联无限科技有限公司 | Distributed transaction processing method based on distributed message middleware |
| CN110719228A (en) * | 2019-08-27 | 2020-01-21 | 中国船舶重工集团公司第七0九研究所 | Large data packet transmission method and device based on real-time data distribution service |
| CN110719228B (en) * | 2019-08-27 | 2022-08-16 | 中国船舶重工集团公司第七0九研究所 | Big data packet transmission method and device based on real-time data distribution service |
| CN110895547A (en) * | 2019-11-29 | 2020-03-20 | 交通银行股份有限公司 | Multi-source heterogeneous database data synchronization system and method based on DB2 federal characteristics |
| CN110895547B (en) * | 2019-11-29 | 2023-09-05 | 交通银行股份有限公司 | Multi-source heterogeneous database data synchronization system and method based on DB2 federation characteristics |
| CN111400053A (en) * | 2020-03-17 | 2020-07-10 | 畅捷通信息技术股份有限公司 | Database access system, method, apparatus and computer-readable storage medium |
| CN111400053B (en) * | 2020-03-17 | 2023-12-15 | 畅捷通信息技术股份有限公司 | Database access system, method, apparatus and computer readable storage medium |
| CN112069160A (en) * | 2020-08-31 | 2020-12-11 | 浙江华瑞信息资讯股份有限公司 | CAP (CAP phase error) data based cleaning synchronization method |
| CN112069160B (en) * | 2020-08-31 | 2023-06-27 | 浙江华瑞信息资讯股份有限公司 | CAP-based data cleaning synchronization method |
| CN112052603B (en) * | 2020-09-25 | 2022-05-20 | 中国直升机设计研究所 | Helicopter-based multi-machine collaborative simulation architecture and data interaction method |
| CN112052603A (en) * | 2020-09-25 | 2020-12-08 | 中国直升机设计研究所 | Helicopter-based multi-machine collaborative simulation architecture and data interaction method |
| CN113722401A (en) * | 2021-11-04 | 2021-11-30 | 树根互联股份有限公司 | Data caching method and device, computer equipment and readable storage medium |
| CN115022392A (en) * | 2022-06-24 | 2022-09-06 | 浪潮软件集团有限公司 | IOT-oriented distributed publishing and subscribing service method and system |
| CN115022392B (en) * | 2022-06-24 | 2024-04-30 | 浪潮软件集团有限公司 | IOT-oriented distributed publishing and subscribing service method and system |
| CN115208899A (en) * | 2022-06-29 | 2022-10-18 | 安阳师范学院 | Improved P2P mass scientific data synchronization method |
| CN115208899B (en) * | 2022-06-29 | 2023-06-06 | 安阳师范学院 | Improved P2P mass scientific data synchronization method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102724304A (en) | Information warehouse federation in subscription/release system and data synchronization method | |
| CN106991113B (en) | Table replication in a database environment | |
| US10747745B2 (en) | Transaction execution commitment without updating of data row transaction status | |
| USRE47106E1 (en) | High-performance log-based processing | |
| US8224860B2 (en) | Database management system | |
| Cowling et al. | Granola:{Low-Overhead} distributed transaction coordination | |
| US8838534B2 (en) | Distributed transaction processing | |
| Kemme et al. | Database replication: a tale of research across communities | |
| CN102037463B (en) | Log based replication of distributed transactions using globally acknowledged commits | |
| CN103870570A (en) | HBase (Hadoop database) data usability and durability method based on remote log backup | |
| Ferro et al. | Omid: Lock-free transactional support for distributed data stores | |
| Moiz et al. | Database replication: A survey of open source and commercial tools | |
| EP4276651A1 (en) | Log execution method and apparatus, and computer device and storage medium | |
| Padhye et al. | Scalable transaction management with snapshot isolation for NoSQL data storage systems | |
| CN115562676B (en) | Triggering method of graph calculation engine | |
| CN101930463A (en) | Memory database-based simulation grid node quick migration method | |
| Rodrigues et al. | The GlobData fault-tolerant replicated distributed object database | |
| Wu et al. | Overview of real-time database management system design for power system scada system | |
| Tomic et al. | MoSQL: An elastic storage engine for MySQL | |
| Stage | Synchronization and replication in the context of mobile applications | |
| Padhye | Transaction and data consistency models for cloud applications | |
| Armendáriz et al. | A recovery protocol for middleware replicated databases providing GSI | |
| Armendáriz et al. | A lock based algorithm for concurrency control and recovery in a middleware replication software architecture | |
| Adly | HARP: a hierarchical asynchronous replication protocol for massively replicated systems | |
| Garcia-Munoz et al. | Recovery Protocols for Replicated Databases--A Survey |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20121010 |