CN106339498A - Method, device and system for synchronizing data - Google Patents
Method, device and system for synchronizing data Download PDFInfo
- Publication number
- CN106339498A CN106339498A CN201610803823.7A CN201610803823A CN106339498A CN 106339498 A CN106339498 A CN 106339498A CN 201610803823 A CN201610803823 A CN 201610803823A CN 106339498 A CN106339498 A CN 106339498A
- Authority
- CN
- China
- Prior art keywords
- data
- field
- message body
- message
- data variation
- 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
Classifications
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method, a device and a system for synchronizing data, relates to the communication field and aims to solve the problem that the prior art cannot achieve data synchronization between heterogeneous databases. The method comprises the following steps: obtaining at least one intermediate message body sent by a data change issuing terminal from a message queue system via a data change consumption terminal, wherein the intermediate message body comprises a message format FORMAT field, a structure version VERSION field, a resource name RESOURCE field, a resource example key value KEY field, an updating type OPERATION field, an updating content CONTENT field, a data issuing terminal identifier PRODUCER field and a data change time PRODUCER-TIME field; obtaining message format FORMAT from the message format FORMAT field of the intermediate message body; analyzing the intermediate message body according to the message format FORMAT; and carrying out data synchronization operation according to the analyzed intermediate message body. Through the technical scheme, the method, the device and the system can be applied to the process of synchronizing the heterogeneous databases.
Description
Technical field
The present invention relates to the communications field, more particularly, to a kind of method of data synchronization, device and system.
Background technology
With the continuous development of internet, between database, need the situation carrying out data syn-chronization more and more universal.Existing
Have in technology, database model species is a lot, and common database model includes: relevant database, the data of non-relational
Storehouse (not only sql, nosql), column database and distributed file system (hadoop distributed file
System, hdfs) etc..Even the database of same model, there is also the Database Systems of a lot of different structures, for example: close
It is that type database includes: relational data management system (mysql), SQL service system (structured
Query language server, sqlserver) and Oracle Database Systems (oracle) etc..
Prior art generally is directed to same model or isomorphism database carries out data syn-chronization, for example: base between mysql
In the synchronization scenario of binary file (bin) daily record, or between mysql and oracle, it is based on tables of data and field mapping synchronization
Scheme etc..
During realizing the present invention, inventor finds, the method for data synchronization that prior art provides only can be same
Carry out data syn-chronization it is impossible to solve the data synchronization problems between heterologous heterogeneous database between model or isomorphism database.
Content of the invention
For synchronous, the embodiment of the present invention that solves the problems, such as that prior art cannot solve heterologous data among heterogeneous databases
A kind of method of data synchronization, device and system are provided.
On the one hand, a kind of method of data synchronization provided in an embodiment of the present invention, comprising: when data changes, data
Change publishing side obtains the relevant information of delta data, and wherein, the relevant information of described delta data includes: resource name
Resource, the key assignments key of resource instances, updating type operation, more new content content, described data variation are issued
The mark producer data transformation period producer_time at end；Described data variation publishing side is according to described change number
According to relevant information generate intermediary message body, wherein, described intermediary message body includes: message format format field, structure version
This version field, resource name resource field, the key assignments key field of resource instances, updating type operation word
Section, more new content content field, data publication end mark producer field data transformation period producer_time
Field；Described data variation publishing side is passed through Message Queuing system and is sent described intermediary message body to data variation consumption terminal.
On the other hand, the embodiment of the present invention provides a kind of method of data synchronization, comprising: data variation consumption terminal is from message team
The intermediary message body of at least one data variation publishing side transmission is obtained, wherein, described intermediary message body includes: disappears in row system
Breath form format field, structure version version field, resource name resource field, the key assignments key word of resource instances
Section, updating type operation field, more new content content field, data publication end mark producer field data
Transformation period producer_time field；Described data variation consumption terminal is from the message format format of described intermediary message body
Field obtains message format format；Described data variation consumption terminal is according to described message format format to described intermediary message
Body is parsed；Described data variation consumption terminal carries out data syn-chronization operation according to the intermediary message body after parsing.
On the other hand, the embodiment of the present invention provides a kind of data variation publishing side, comprising:
Acquisition module, for when data changes, obtaining the relevant information of delta data, wherein, described change number
According to relevant information include: resource name resource, the key assignments key of resource instances, updating type operation, update in
Hold content, the mark producer data transformation period producer_time of described data variation publishing side；
Generation module, the relevant information of the described delta data for being obtained according to described acquisition module generates intermediary message
Body, wherein, described intermediary message body includes: message format format field, structure version version field, resource name
Resource field, the key assignments key field of resource instances, updating type operation field, more new content content field,
Data publication end identifies producer field data transformation period producer_time field；
Sending module, sending module, for sending described generation mould by Message Queuing system to data variation consumption terminal
The intermediary message body that block generates.
On the other hand, the embodiment of the present invention provides a kind of data variation consumption terminal, comprising:
First acquisition module, for obtaining the centre of at least one data variation publishing side transmission from Message Queuing system
Message body, wherein, described intermediary message body includes: message format format field, structure version version field, resource name
Claim resource field, the key assignments key field of resource instances, updating type operation field, more new content content word
Section, data publication end mark producer field data transformation period producer_time field；
Second acquisition module, for obtaining message format from the message format format field of described intermediary message body
format；
Parsing module, for according to described second acquisition module obtain message format format to described intermediary message body
Parsed；
Synchronization module, for carrying out data syn-chronization operation according to the intermediary message body after the parsing of described parsing module.
On the other hand, a kind of data synchronous system provided in an embodiment of the present invention, comprising: at least one data variation is issued
End, Message Queuing system and at least one data variation consumption terminal；Wherein,
Described data variation publishing side, for when data changes, obtaining the relevant information of delta data, wherein,
The relevant information of described delta data includes: resource name resource, the key assignments key of resource instances, updating type
Operation, more new content content, the mark producer data transformation period of described data variation publishing side
Producer_time, the relevant information according to described delta data generates intermediary message body, wherein, described intermediary message body bag
Include: message format format field, structure version version field, resource name resource field, the key assignments of resource instances
Key field, updating type operation field, more new content content field, data publication end mark producer field
Data transformation period producer_time field, sends described intermediary message body to described Message Queuing system；
Described Message Queuing system, after being used for receiving described intermediary message body, real from the resource of described intermediary message body
The key assignments key that the key assignments key field of example obtains resource instances simultaneously stores, according to the subscribing relationship list pre-setting, obtain to
A few data variation consumption terminal, described intermediary message body is sent at least one described data variation consumption terminal；
Described data variation consumption terminal, for obtaining intermediary message body from Message Queuing system, from described intermediary message
The message format format field of body obtains message format format, according to described message format format to described intermediary message
Body is parsed, and carries out data syn-chronization operation according to the intermediary message body after parsing.
Method of data synchronization provided in an embodiment of the present invention, device and system, by having the intermediary message of set form
Body transmits the relevant information of delta data, because the structure of intermediary message body is to pre-set so that data passes through process
Can carry out between heterologous heterogeneous database, solving prior art cannot be in the synchronization of heterologous data among heterogeneous databases
Problem.
Brief description
By reading the detailed description that non-limiting example is made made with reference to the following drawings, other of the application
Feature, objects and advantages will become more apparent upon:
Fig. 1 is method of data synchronization flow chart provided in an embodiment of the present invention；
Fig. 2 is the flow chart one of step 102 in the method for data synchronization provided in an embodiment of the present invention shown in Fig. 1；
Fig. 3 is the flowchart 2 of step 102 in the method for data synchronization provided in an embodiment of the present invention shown in Fig. 1；
Fig. 4 is the flow chart one of step 103 in the method for data synchronization provided in an embodiment of the present invention shown in Fig. 1；
Fig. 5 be in the step 103 shown in Fig. 4 Message Queuing system in one-to-one mode in data variation publishing side data
Carry out the schematic diagram of intermediary message body transmission between change consumption terminal；
Fig. 6 be in the step 103 shown in Fig. 4 Message Queuing system with one-to-many manner in data variation publishing side data
Carry out the schematic diagram of intermediary message body transmission between change consumption terminal；
Fig. 7 be in the step 103 shown in Fig. 4 Message Queuing system in many-one mode in data variation publishing side data
Carry out the schematic diagram of intermediary message body transmission between change consumption terminal；
Fig. 8 be in the step 103 shown in Fig. 4 Message Queuing system with multipair multimode in data variation publishing side data
Carry out the schematic diagram of intermediary message body transmission between change consumption terminal；
Fig. 9 is the flowchart 2 of step 103 in the method for data synchronization provided in an embodiment of the present invention shown in Fig. 1；
Figure 10 be in the step 103 shown in Fig. 9 Message Queuing system with one-to-many manner in data variation publishing side sum
According to the schematic diagram carrying out intermediary message body transmission between change consumption terminal；
Figure 11 be in the step 103 shown in Fig. 9 Message Queuing system with one-to-many manner in data variation publishing side sum
According to the schematic diagram carrying out intermediary message body transmission between change consumption terminal；
Figure 12 be in the step 103 shown in Fig. 9 Message Queuing system in many-one mode in data variation publishing side sum
According to the schematic diagram carrying out intermediary message body transmission between change consumption terminal；
Figure 13 be in the step 103 shown in Fig. 9 Message Queuing system with multipair multimode in data variation publishing side sum
According to the schematic diagram carrying out intermediary message body transmission between change consumption terminal；
Figure 14 is the flow chart 3 of step 103 in the method for data synchronization provided in an embodiment of the present invention shown in Fig. 1；
Figure 15 is the method for data synchronization flow chart one that another embodiment of the present invention provides；
Figure 16 is the flow chart of step 1504 in the method for data synchronization that the another embodiment of the present invention shown in Figure 15 provides
One；
Figure 17 is the flow chart of step 1504 in the method for data synchronization that the another embodiment of the present invention shown in Figure 15 provides
Two；
Figure 18 is the method for data synchronization flowchart 2 that another embodiment of the present invention provides；
Figure 19 is the structural representation of data variation publishing side provided in an embodiment of the present invention；
Figure 20 is the structural representation one of generation module 1902 in data variation publishing side described in Figure 19；
Figure 21 is the structural representation two of generation module 1902 in data variation publishing side described in Figure 19；
Figure 22 is the structural representation one of data variation consumption terminal provided in an embodiment of the present invention；
Figure 23 is the structural representation one of synchronization module 2204 in the data variation consumption terminal shown in Figure 22；
Figure 24 is the structural representation two of synchronization module 2204 in the data variation consumption terminal shown in Figure 22；
Figure 25 is the structural representation of the first acquisition module 2201 in the data variation consumption terminal shown in Figure 22；
Figure 26 is the structural representation two of data variation consumption terminal provided in an embodiment of the present invention；
Figure 27 is the structural representation of data synchronous system provided in an embodiment of the present invention.
Specific embodiment
With reference to the accompanying drawings and examples the application is described in further detail.It is understood that this place is retouched
The specific embodiment stated is used only for explaining related invention, rather than the restriction to this invention.It also should be noted that, in order to
It is easy to describe, illustrate only in accompanying drawing and invent related part.
It should be noted that in the case of not conflicting, the embodiment in the application and the feature in embodiment can phases
Mutually combine.To describe the application below with reference to the accompanying drawings and in conjunction with the embodiments in detail.
For synchronous, the embodiment of the present invention that solves the problems, such as that prior art cannot solve heterologous data among heterogeneous databases
A kind of method of data synchronization, device and system are provided.
As shown in figure 1, a kind of method of data synchronization provided in an embodiment of the present invention, comprising:
Step 101, when data changes, data variation publishing side obtains the relevant information of delta data, wherein, becomes
The relevant information changing data includes: resource name resource, the key assignments key of resource instances, updating type operation, more
New content content, the mark producer data transformation period producer_time of described data variation publishing side.
Step 102, data variation publishing side generates intermediary message body according to the relevant information of delta data, wherein, middle
Message body includes: message format format field, structure version version field, resource name resource field, resource are real
The key assignments key field of example, updating type operation field, more new content content field, data publication end mark
Producer field data transformation period producer_time field.
Below each field that middle message body comprises is described in detail:
1st, message format format field
This field is mandatory field, and for indicating the encapsulation format of intermediary message body, this field type is character string, value
Scope includes: javascript object representation (javascript object notation, json), extensible markup language
(extensible markup language, xml) and text formatting (text), for example:
format:‘json’
format:‘xml’
format:‘text’
During actual use, message format format word can be pre-set according to actual communication system requirements
It is also possible to be not provided with, now, the value of message format format field is default value json to the value of section.
2nd, structure version version field
This field is mandatory field, and for representing the numbering of message body, this field type is character string, and span is non-
Null character string, for example:
version:1.0
version:1.0alpha
3rd, resource name resource field
This field is mandatory field, for carrying out unified definition to resource name, and in data variation publishing side data
Shared between change consumption terminal, this field type is character string, and span is nonblank character string, this character string and resource name
There is one-to-one relationship, for example:
resource:sns_account
resource:sns_tweet
4th, the key assignments key field of resource instances
This field is mandatory field, for determining the data resource example of data variation impact, wherein, data resource example
Can it be 1 or multiple, this field type is array (dictionary structure), and span includes: 1 or multiple entry name
Claim, for example:
The structure of arrays of key is specifically as follows as shown in table 1 below:
Table 1
5th, updating type operation field
This field is mandatory field, the data variation action type supported for instruction, and this field type is character string, takes
Value scope includes: updates (uppdate), insertion (insert), deletes (delete) and update insertion (upsert), for example:
operation:‘update’
operation:‘upsert’
operation:‘insert’
operation:‘delete’
6th, more new content content field
This field is mandatory field, and for describing the more new content of data, this field type is array (dictionary structure), uses
The dictionary result description of key-value, span includes: the corresponding more new content of one or more projects, for example: update micro-
The literary composition time of pusher of letter account
content:{
‘last_update_time’:‘1203984004’
}
Wherein, key is last_update_time, and the value value of the corresponding content of key is 1203984004.
7th, data publication end mark producer field
This field is mandatory field, for unique mark is carried out to data variation publishing side, so that log, this field
Type is character string, and span is non-NULL and significant common text strings, for example:
producer:‘wechat_daily_crawler’
8th, data variation time producer_time field
This field is mandatory field, and for record data transformation period, this field type is integer, and span is
Unixtime timestamp, precision to second, for example:
producer_time:‘1489080439’
In order that those skilled in the art can be more clearly understood that the implementation method of step 102, as shown in Fig. 2 step
102 specifically may include that
Step 201, data variation publishing side updating type to middle message body according to updating type operation
Operation field carries out assignment.
Specifically, if changing content is to update available data, then operation field is entered as update；As
Fruit changing content is one new data content of insertion, then operation word is entered as insert；If changing content is
Insertion updates a data content, then operation field is entered as upsert；If changing content is to have deleted one
Some data contents, then operation field is entered as delete.
Step 202, data variation publishing side resource name to middle message body according to resource name resource
Resource field carries out assignment.
During actual use, resource adopts enumeration type, and its value is from the resource type pre-setting
Choose in list.Wherein, resource type list is to be arranged according to application scenarios, for example: application scenarios are social media number
During according to exchange process, the Resources list could be arranged to account essential information (account) and blog article essential information (tweet), this
When, the assignment of resource field can be only account or tweet.
Step 203, the key of data variation publishing side resource instances to middle message body according to the key assignments key of resource instances
Value key field carries out assignment.
In the present embodiment, the key assignments key of resource instances is the unique mark of the destination object that data variation occurs.Middle
The key assignments key field value of the resource instances of message body is typically a nested dictionary structure, the key assignments key word of resource instances
Each field of section and value is a key-value pair it is determined that the destination object of only one or multiple data variation.
Step 204, data variation publishing side more new content to middle message body according to more new content content
Content field carries out assignment.
In the present embodiment, more new content content is the data change of the key assignments key instruction of resource instances in step 203
The data variation content of the destination object changed.The more new content content field of intermediary message body is by one or more key assignments
To composition, it is relation arranged side by side between each key-value pair, each key-value pair identifies the content of a data variation, and requires this
A little changes must be applied in data storage simultaneously.
Step 205, data variation publishing side is according to the mark producer data transformation period of data variation publishing side
Producer_time identifies producer field data transformation period to the data publication end of middle message body respectively
Producer_time field carries out assignment.
Step 206, data variation publishing side obtains structure version version of intermediary message body, according to structure version
Version carries out assignment to the structure version version field of middle message body.
Step 207, data variation publishing side obtains message format from the message format format field of middle message body
Format, is packaged to the intermediary message body after assignment according to message format format.
During actual use, the data synchronization process between database is typically conditional on, in order to solve
The data synchronization problems between heterologous heterogeneous database under the premise of condition, further, data provided in an embodiment of the present invention
In synchronous method, the relevant information of delta data can also include: data updates execution condition condition, intermediary message body
Can also include: data updates execution condition condition field.
Then now, as shown in figure 3, step 102 can also include:
Step 208, data variation publishing side updates the data to middle message body for execution condition condition according to data
Update execution condition condition field and carry out assignment.
In the present embodiment, data updates execution condition condition field is Optional Field, for indicating data variation
Condition, this field type be array (dictionary structure), span can support complexity bohr operator (for example: and,
Or or nor etc.) connect multiple conditions, for example:
condition:{
last_update_time:{“$gt”:1203984004}
}
The data structure of data renewal execution condition condition field is specifically as follows as shown in table 2 below:
Table 2
Particularly, the value that data updates execution condition condition field can be sky, now, for unconditional state.
It should be noted that step 208 can be carried out any position before step 207, the present embodiment is only with step
208 after step 206, and step 207 illustrates as a example before.
Step 103, data variation publishing side is passed through Message Queuing system and is sent intermediary message body to data variation consumption terminal.
Specifically, as shown in figure 4, step 103 may include that
Step 401, data variation publishing side sends intermediary message body to Message Queuing system.
Step 402, the key assignments key field of the resource instances from middle message body for the Message Queuing system obtains resource instances
Key assignments key simultaneously stores.
Specifically, Message Queuing system can carry out the calculating of hash value to middle message body, therefrom obtains resource instances
Key assignments key is simultaneously stored in internal memory.
Step 403, Message Queuing system, according to the subscribing relationship list pre-setting, obtains at least one data variation and disappears
Fei Duan.
Step 404, intermediary message body is sent at least one data variation consumption terminal by Message Queuing system.
In the present embodiment, Message Queuing system can all put into the intermediary message receiving body in one queue, and
According to FIFO principle, order sends intermediary message body.Now, Message Queuing system can become in data in several ways
Change publishing side data and change and carry out intermediary message body transmission, for example between consumption terminal: one-to-one mode as shown in Figure 5, such as
One-to-many manner shown in Fig. 6, many-one mode as shown in Figure 7, or multipair multimode as shown in Figure 9 etc..
Preferably, in order to improve the efficiency of transmission of data further, reach the purpose of efficient transfer data, the present invention is implemented
Example provide method of data synchronization in Message Queuing system can by multiplexing, concurrent by way of carry out data transmission.
In order to achieve the above object, as shown in figure 9, step 103 can also include:
Step 405, Message Queuing system pre-sets at least one message queue.
Then now, step 404 specifically may include that
Step 4041, intermediary message body is sent in corresponding message queue for Message Queuing system.
Step 4042, intermediary message body is sent at least one data variation by message queue and disappears by Message Queuing system
Fei Duan.
Because Message Queuing system pre-sets multiple message queues so that Message Queuing system can will receive
Intermediary message body is sent in different message queues, between different message queues can with concurrent transmission intermediary message body, from
And reach the purpose of high efficiency of transmission.
Further, because Message Queuing system pre-sets multiple message queues so that Message Queuing system is permissible
Carry out intermediary message body transmission between data variation publishing side data change consumption terminal in several ways, for example: as schemed
One-to-one mode shown in 10, one-to-many manner as shown in figure 11, many-one mode as shown in figure 12, or as Figure 13 institute
Multipair multimode shown etc..
Further, in order to ensure the success rate that intermediary message body is sent to, as shown in figure 14, step 103 can also include:
Step 406, Message Queuing system's receiving data changes the data variation confirmation response message that consumption terminal sends.
Step 407, Message Queuing system confirms response message according to data variation, removes the key assignments key of resource instances.
Method of data synchronization provided in an embodiment of the present invention, transmits change number by the intermediary message body with set form
According to relevant information, because the structure of intermediary message body is to pre-set so that data can be heterologous different by process
Carry out between structure database, solve the problems, such as that prior art cannot be synchronous in heterologous data among heterogeneous databases.
As shown in figure 15, another embodiment of the present invention also provides a kind of method of data synchronization, comprising:
Step 1501, data variation consumption terminal obtains at least one data variation publishing side from Message Queuing system and sends
Intermediary message body, wherein, intermediary message body includes: message format format field, structure version version field, resource
Title resource field, the key assignments key field of resource instances, updating type operation field, more new content content
Field, data publication end mark producer field data transformation period producer_time field.
Being discussed in detail of each field of intermediary message body described in the present embodiment may refer to described in the step 101 shown in Fig. 1,
Here is omitted.
Specifically, in the present embodiment, step 1501 can obtain intermediary message body by two ways.
One kind is: data variation consumption terminal receives at least one data variation publishing side that Message Queuing system actively sends
The intermediary message body sending.
Another kind is: data variation consumption terminal sends intermediary message body request message to described Message Queuing system, and connects
During receipts Message Queuing system sends according at least one data variation publishing side that described intermediary message body request message returns
Between message body.
Certainly, both the above form is only specific and illustrates, and during actual use, data variation consumption terminal also may be used
To obtain intermediary message body by other means, every kind of situation is not repeated one by one herein.
Step 1502, data variation consumption terminal obtains message format from the message format format field of middle message body
format.
Step 1503, data variation consumption terminal parses to middle message body according to message format format.
Step 1504, data variation consumption terminal carries out data syn-chronization operation according to the intermediary message body after parsing.
Specifically, as shown in figure 16, step 1504 may include that
Step 1601, data variation consumption terminal analytically after intermediary message body structure version version field obtain
Structure version version.
Step 1602, data variation consumption terminal searches, according to structure version version, the version coding schedule prestoring.
Step 1603, if data variation consumption terminal finds structure version version from version coding schedule, data becomes
Change consumption terminal and data syn-chronization operation is carried out according to the intermediary message body after parsing.
Step 1604, otherwise, data variation consumption terminal stops data syn-chronization misregistration daily record.
Further, if intermediary message body also includes: data updates execution condition condition field, as Figure 17 institute
Show, step 1504 can also include:
Step 1605, data variation consumption terminal analytically after intermediary message body data update execution condition
Condition field obtains data and updates execution condition condition.
Step 1606, if meet data to update execution condition condition, after data variation consumption terminal is according to parsing
Intermediary message body carries out data syn-chronization operation.
Step 1607, otherwise, data variation consumption terminal stops data syn-chronization misregistration daily record.
Further, as shown in figure 18, the method for data synchronization that another embodiment of the present invention provides, can also include:
Step 1505, when data syn-chronization success, data variation consumption terminal sends data variation to breath queue system and confirms
Response message.
Method of data synchronization provided in an embodiment of the present invention, transmits change number by the intermediary message body with set form
According to relevant information, because the structure of intermediary message body is to pre-set so that data can be heterologous different by process
Carry out between structure database, solve the problems, such as that prior art cannot be synchronous in heterologous data among heterogeneous databases.
As shown in figure 19, the embodiment of the present invention also provides a kind of data variation publishing side, comprising:
Acquisition module 1901, for when data changes, obtaining the relevant information of delta data, wherein, described change
The relevant information changing data includes: resource name resource, the key assignments key of resource instances, updating type operation, more
New content content, the mark producer data transformation period producer_time of described data variation publishing side；
Generation module 1902, the relevant information of the described delta data for being obtained according to described acquisition module 1901 generates
Intermediary message body, wherein, described intermediary message body includes: message format format field, structure version version field, money
Source name resource field, the key assignments key field of resource instances, updating type operation field, more new content
Content field, data publication end mark producer field data transformation period producer_time field；
Sending module 1903, for sending described generation module 1902 by Message Queuing system to data variation consumption terminal
The intermediary message body generating.
Further, as shown in figure 20, generation module 1902 may include that
First assignment submodule 2001, for according to described updating type operation to described intermediary message body more
New type operation field carries out assignment；
Second assignment submodule 2001, for the resource to described intermediary message body according to described resource name resource
Title resource field carries out assignment；
3rd assignment submodule 2003, for the money to described intermediary message body for the key assignments key according to described resource instances
The key assignments key field of source instance carries out assignment；
4th assignment submodule 2004, for the renewal to described intermediary message body according to described more new content content
Content content field carries out assignment；
5th assignment submodule 2005, for the mark producer data change according to described data variation publishing side
When time producer_time changes to the data publication end mark producer field data of described intermediary message body respectively
Between producer_time field carry out assignment；
6th assignment submodule 2006, for obtaining structure version version of described intermediary message body, according to described knot
Structure version version carries out assignment to the structure version version field of described intermediary message body；
Encapsulation submodule 2007, for obtaining message format from the message format format field of described intermediary message body
Format, according to described message format format field to by described first assignment submodule 2001 to the 6th assignment submodule
Described intermediary message body after 2006 assignment is packaged.
Further, as shown in figure 21, generation module 1902 can also also include:
7th assignment submodule 2008, if the relevant information of described delta data also includes: data updates execution condition
Condition, described intermediary message body also includes: data updates execution condition condition field, for according to described data
Update execution condition condition and assignment is carried out to the data renewal execution condition condition field of described intermediary message body.
The concrete methods of realizing of data variation publishing side provided in an embodiment of the present invention may refer to as represented in figures 1 through 14
Described in method of data synchronization provided in an embodiment of the present invention, here is omitted.
Data variation publishing side provided in an embodiment of the present invention, transmits change by the intermediary message body with set form
The relevant information of data, because the structure of intermediary message body is to pre-set so that data can be heterologous by process
Carry out between heterogeneous database, solve the problems, such as that prior art cannot be synchronous in heterologous data among heterogeneous databases.
As shown in figure 22, the embodiment of the present invention also provides a kind of data variation consumption terminal, comprising:
First acquisition module 2201, for obtaining the transmission of at least one data variation publishing side from Message Queuing system
Intermediary message body, wherein, described intermediary message body includes: message format format field, structure version version field, money
Source name resource field, the key assignments key field of resource instances, updating type operation field, more new content
Content field, data publication end mark producer field data transformation period producer_time field；
Second acquisition module 2202, for obtaining message format from the message format format field of described intermediary message body
format；
Parsing module 2203, for the message format format that obtained according to described second acquisition module 2202 in described
Between message body parsed；
Synchronization module 2204, for carrying out data syn-chronization behaviour according to the intermediary message body after the parsing of described parsing module 2203
Make.
Further, as shown in figure 23, synchronization module 2204 may include that
First acquisition submodule 2301, for the structure version version field of the intermediary message body after described parsing
Obtain structure version version；
Search submodule 2302, for looking into according to structure version version that described first acquisition submodule 2301 obtains
Look for the version coding schedule prestoring；
Synchronous submodule 2303, if find described from described version coding schedule for described lookup submodule 2302
Structure version version, carries out data syn-chronization operation according to the intermediary message body after parsing；
Record sub module 2304, if do not find institute for described lookup submodule 2302 from described version coding schedule
State structure version version, stop data syn-chronization misregistration daily record.
Further, as shown in figure 24, synchronization module 2204 can also include:
Second acquisition submodule 2305, the data for the intermediary message body after described parsing updates execution condition
Condition field obtains data and updates execution condition condition；
Then described synchronous submodule 2303 is additionally operable to, if meeting described data to update execution condition condition, according to
Intermediary message body after parsing carries out data syn-chronization operation；
Described record sub module 2304, if being additionally operable to be unsatisfactory for described data renewal execution condition condition, stops
Data syn-chronization misregistration daily record.
Further, as shown in figure 25, the first acquisition module 2201 may include that
First communication submodule 2501, for receiving at least one described data that described Message Queuing system actively sends
The intermediary message body that change publishing side sends；Or,
Second communication submodule 2502, for sending intermediary message body request message to described Message Queuing system, and connects
Receive at least one described data variation publishing side that described Message Queuing system returns according to described intermediary message body request message
The intermediary message body sending.
Further, as shown in figure 26, data variation consumption terminal provided in an embodiment of the present invention, can also include:
Sending module 2205, for when described synchronization module 2204 carries out data syn-chronization success, to described message queue
System sends data variation and confirms response message.
The concrete methods of realizing of data variation consumption terminal provided in an embodiment of the present invention may refer to as shown in Figure 15-21
Described in method of data synchronization, here is omitted.
Data variation consumption terminal provided in an embodiment of the present invention, transmits change by the intermediary message body with set form
The relevant information of data, because the structure of intermediary message body is to pre-set so that data can be heterologous by process
Carry out between heterogeneous database, solve the problems, such as that prior art cannot be synchronous in heterologous data among heterogeneous databases.
As shown in figure 27, the embodiment of the present invention also provides a kind of data synchronous system, comprising: at least one data variation is sent out
Cloth end 2701, Message Queuing system 2702 and at least one data variation consumption terminal 2703；Wherein,
Described data variation publishing side 2701, for when data changes, obtaining the relevant information of delta data, its
In, the relevant information of described delta data includes: resource name resource, the key assignments key of resource instances, updating type
Operation, more new content content, the mark producer data transformation period of described data variation publishing side
Producer_time, the relevant information according to described delta data generates intermediary message body, wherein, described intermediary message body bag
Include: message format format field, structure version version field, resource name resource field, the key assignments of resource instances
Key field, updating type operation field, more new content content field, data publication end mark producer field
Data transformation period producer_time field, sends described intermediary message body to described Message Queuing system 2702；
Described Message Queuing system 2702, after being used for receiving described intermediary message body, from the money of described intermediary message body
The key assignments key field of source instance obtains the key assignments key of resource instances and stores, and according to the subscribing relationship list pre-setting, obtains
Take at least one data variation consumption terminal 2703, described intermediary message body is sent at least one described data variation consumption terminal
2703；
Described data variation consumption terminal 2703, for obtaining intermediary message body from Message Queuing system 2702, from described
The message format format field of intermediary message body obtains message format format, according to described message format format to described
Intermediary message body is parsed, and carries out data syn-chronization operation according to the intermediary message body after parsing.
The concrete methods of realizing of data synchronous system provided in an embodiment of the present invention may refer to the number as shown in Fig. 1-2 1
According to described in synchronous method, here is omitted.
Data synchronous system provided in an embodiment of the present invention, transmits change number by the intermediary message body with set form
According to relevant information, because the structure of intermediary message body is to pre-set so that data can be heterologous different by process
Carry out between structure database, solve the problems, such as that prior art cannot be synchronous in heterologous data among heterogeneous databases.
Above description is only the preferred embodiment of the application and the explanation to institute's application technology principle.People in the art
Member is it should be appreciated that involved invention scope is however it is not limited to the technology of the particular combination of above-mentioned technical characteristic in the application
Scheme, also should cover simultaneously in the case of without departing from described inventive concept, be carried out by above-mentioned technical characteristic or its equivalent feature
The other technical schemes being combined and being formed.Such as features described above has similar work(with (but not limited to) disclosed herein
The technical scheme that the technical characteristic of energy is replaced mutually and formed.
Claims (20)
1. a kind of method of data synchronization is it is characterised in that include:
When data changes, data variation publishing side obtains the relevant information of delta data, wherein, described delta data
Relevant information includes: resource name resource, the key assignments key of resource instances, updating type operation, more new content
Content, the mark producer data transformation period producer_time of described data variation publishing side；
Described data variation publishing side generates intermediary message body, wherein, described centre according to the relevant information of described delta data
Message body includes: message format format field, structure version version field, resource name resource field, resource are real
The key assignments key field of example, updating type operation field, more new content content field, data publication end mark
Producer field data transformation period producer_time field；
Described data variation publishing side is passed through Message Queuing system and is sent described intermediary message body to data variation consumption terminal.
2. method according to claim 1 is it is characterised in that described data variation publishing side is according to described delta data
Relevant information generates intermediary message body and includes:
Described data variation publishing side updating type to described intermediary message body according to described updating type operation
Operation field carries out assignment；
Described data variation publishing side resource name to described intermediary message body according to described resource name resource
Resource field carries out assignment；
The key of described data variation publishing side resource instances to described intermediary message body according to the key assignments key of described resource instances
Value key field carries out assignment；
Described data variation publishing side more new content to described intermediary message body according to described more new content content
Content field carries out assignment；
Described data variation publishing side is according to the mark producer data transformation period of described data variation publishing side
Producer_time identifies producer field data transformation period to the data publication end of described intermediary message body respectively
Producer_time field carries out assignment；
Described data variation publishing side obtains structure version version of described intermediary message body, according to described structure version
Version carries out assignment to the structure version version field of described intermediary message body；
Described data variation publishing side obtains message format from the message format format field of described intermediary message body
Format, is packaged to the described intermediary message body after assignment according to described message format format.
3. method according to claim 2 is it is characterised in that the relevant information of described delta data also includes: data is more
New execution condition condition, described intermediary message body also includes: data updates execution condition condition field；
Then described data variation publishing side generates intermediary message body according to the relevant information of described delta data and also includes:
Described data variation publishing side updates the data to described intermediary message body for execution condition condition according to described data
Update execution condition condition field and carry out assignment.
4. method according to claim 1 it is characterised in that described data variation publishing side pass through Message Queuing system to
Data variation consumption terminal sends described intermediary message body and includes:
Described data variation publishing side sends described intermediary message body to described Message Queuing system；
The key assignments key field of the resource instances from described intermediary message body for the described Message Queuing system obtains the key assignments of resource instances
Key simultaneously stores；
Described Message Queuing system, according to the subscribing relationship list pre-setting, obtains at least one data variation consumption terminal；
Described intermediary message body is sent at least one described data variation consumption terminal by described Message Queuing system.
5. method according to claim 4 it is characterised in that described data variation publishing side pass through Message Queuing system to
Data variation consumption terminal sends described intermediary message body and also includes:
Described Message Queuing system pre-sets at least one message queue；
Then described intermediary message body is sent at least one described data variation consumption terminal and includes by described Message Queuing system:
Described intermediary message body is sent in corresponding message queue for described Message Queuing system；
Described intermediary message body is sent at least one described data by described message queue and becomes by described Message Queuing system
Change consumption terminal.
6. method according to claim 4 it is characterised in that described data variation publishing side pass through Message Queuing system to
Data variation consumption terminal sends described intermediary message body and also includes:
Described Message Queuing system receives the data variation confirmation response message that described data variation consumption terminal sends；
Described Message Queuing system confirms response message according to described data variation, removes the key assignments key of described resource instances.
7. a kind of method of data synchronization is it is characterised in that include:
Data variation consumption terminal obtains the intermediary message body of at least one data variation publishing side transmission from Message Queuing system,
Wherein, described intermediary message body includes: message format format field, structure version version field, resource name
Resource field, the key assignments key field of resource instances, updating type operation field, more new content content field,
Data publication end identifies producer field data transformation period producer_time field；
Described data variation consumption terminal obtains message format format from the message format format field of described intermediary message body；
Described data variation consumption terminal parses to described intermediary message body according to described message format format；
Described data variation consumption terminal carries out data syn-chronization operation according to the intermediary message body after parsing.
8. method according to claim 7 is it is characterised in that described data variation consumption terminal disappears according to the centre after parsing
Breath body carries out data syn-chronization operation and includes:
The structure version version field of intermediary message body after described parsing for the described data variation consumption terminal obtains structure version
This version；
Described data variation consumption terminal searches, according to described structure version version, the version coding schedule prestoring；
If described data variation consumption terminal finds described structure version version, described number from described version coding schedule
According to change consumption terminal, data syn-chronization operation is carried out according to the intermediary message body after parsing；
Otherwise, described data variation consumption terminal stops data syn-chronization misregistration daily record.
If 9. method according to claim 8 is it is characterised in that described intermediary message body also includes: data updates to be held
Row condition condition field；
Then described data variation consumption terminal according to parsing after intermediary message body carry out data syn-chronization operation also include:
The data of intermediary message body after described parsing for the described data variation consumption terminal updates execution condition condition field
Obtain data and update execution condition condition；
If meeting described data to update execution condition condition, described data variation consumption terminal is according to the centre after parsing
Message body carries out data syn-chronization operation；
Otherwise, described data variation consumption terminal stops data syn-chronization misregistration daily record.
10. method according to claim 7 is it is characterised in that described data variation consumption terminal is from Message Queuing system
The intermediary message body obtaining the transmission of at least one data variation publishing side includes:
Described data variation consumption terminal receives at least one described data variation issue that described Message Queuing system actively sends
The intermediary message body that end sends；Or,
Described data variation consumption terminal sends intermediary message body request message to described Message Queuing system, and receives described message
The centre that queue system sends according at least one described data variation publishing side that described intermediary message body request message returns
Message body.
11. according to any one of claims of claim 7-10 method it is characterised in that also including:
When data syn-chronization success, described data variation consumption terminal sends data variation to described Message Queuing system and confirms response
Message.
A kind of 12. data variation publishing sides are it is characterised in that include:
Acquisition module, for when data changes, obtaining the relevant information of delta data, wherein, described delta data
Relevant information includes: resource name resource, the key assignments key of resource instances, updating type operation, more new content
Content, the mark producer data transformation period producer_time of described data variation publishing side；
Generation module, the relevant information of the described delta data for being obtained according to described acquisition module generates intermediary message body,
Wherein, described intermediary message body includes: message format format field, structure version version field, resource name
Resource field, the key assignments key field of resource instances, updating type operation field, more new content content field,
Data publication end identifies producer field data transformation period producer_time field；
Sending module, for being disappeared by the centre that Message Queuing system sends described generation module generation to data variation consumption terminal
Breath body.
13. data variation publishing sides according to claim 12 are it is characterised in that described generation module includes:
First assignment submodule, for the updating type to described intermediary message body according to described updating type operation
Operation field carries out assignment；
Second assignment submodule, for the resource name to described intermediary message body according to described resource name resource
Resource field carries out assignment；
3rd assignment submodule, for the key assignments key according to described resource instances to the resource instances of described intermediary message body
Key assignments key field carries out assignment；
4th assignment submodule, for the more new content to described intermediary message body according to described more new content content
Content field carries out assignment；
5th assignment submodule, for the mark producer data transformation period according to described data variation publishing side
Producer_time identifies producer field data transformation period to the data publication end of described intermediary message body respectively
Producer_time field carries out assignment；
6th assignment submodule, for obtaining structure version version of described intermediary message body, according to described structure version
Version carries out assignment to the structure version version field of described intermediary message body；
Encapsulation submodule, for obtaining message format format from the message format format field of described intermediary message body,
According to described message format format field to the institute after described first assignment submodule to the 6th assignment submodule assignment
State intermediary message body to be packaged.
14. data variation publishing sides according to claim 13 are it is characterised in that described generation module also includes:
7th assignment submodule, if the relevant information of described delta data also includes: data updates execution condition
Condition, described intermediary message body also includes: data updates execution condition condition field, for according to described data
Update execution condition condition and assignment is carried out to the data renewal execution condition condition field of described intermediary message body.
A kind of 15. data variation consumption terminals are it is characterised in that include:
First acquisition module, for obtaining the intermediary message of at least one data variation publishing side transmission from Message Queuing system
Body, wherein, described intermediary message body includes: message format format field, structure version version field, resource name
Resource field, the key assignments key field of resource instances, updating type operation field, more new content content field,
Data publication end identifies producer field data transformation period producer_time field；
Second acquisition module, for obtaining message format format from the message format format field of described intermediary message body；
Parsing module, for carrying out to described intermediary message body according to the message format format that described second acquisition module obtains
Parsing；
Synchronization module, for carrying out data syn-chronization operation according to the intermediary message body after the parsing of described parsing module.
16. data variation consumption terminals according to claim 15 are it is characterised in that described synchronization module includes:
First acquisition submodule, the structure version version field for the intermediary message body after described parsing obtains structure
Version version；
Search submodule, the structure version version lookup for obtaining according to described first acquisition submodule prestores
Version coding schedule；
Synchronous submodule, if find described structure version for described lookup submodule from described version coding schedule
Version, carries out data syn-chronization operation according to the intermediary message body after parsing；
Record sub module, if do not find described structure version for described lookup submodule from described version coding schedule
Version, stops data syn-chronization misregistration daily record.
17. data variation consumption terminals according to claim 16 are it is characterised in that described synchronization module also includes:
Second acquisition submodule, the data for the intermediary message body after described parsing updates execution condition condition word
Section obtains data and updates execution condition condition；
Then described synchronous submodule is additionally operable to, if meeting described data to update execution condition condition, after parsing
Intermediary message body carries out data syn-chronization operation；
Described record sub module, if being additionally operable to be unsatisfactory for described data renewal execution condition condition, stops data syn-chronization
And misregistration daily record.
18. data variation consumption terminals according to claim 15 are it is characterised in that described first acquisition module includes:
First communication submodule, issues for receiving at least one described data variation that described Message Queuing system actively sends
The intermediary message body that end sends；Or,
Second communication submodule, for sending intermediary message body request message to described Message Queuing system, and disappears described in receiving
During breath queue system sends according at least one described data variation publishing side that described intermediary message body request message returns
Between message body.
The 19. data variation consumption terminals according to any one in claim 15-18 are it is characterised in that also include:
Sending module, for when described synchronization module carries out data syn-chronization success, sending data to described Message Queuing system
Change confirms response message.
A kind of 20. data synchronous systems it is characterised in that include: at least one data variation publishing side, Message Queuing system and
At least one data variation consumption terminal；Wherein,
Described data variation publishing side, for when data changes, obtaining the relevant information of delta data, wherein, described
The relevant information of delta data includes: resource name resource, the key assignments key of resource instances, updating type operation,
More new content content, the mark producer data transformation period producer_time of described data variation publishing side,
Relevant information according to described delta data generates intermediary message body, and wherein, described intermediary message body includes: message format
Format field, structure version version field, resource name resource field, the key assignments key field of resource instances, more
New type operation field, more new content content field, the mark producer field data change of data publication end
Time producer_time field, sends described intermediary message body to described Message Queuing system；
Described Message Queuing system, after being used for receiving described intermediary message body, from the resource instances of described intermediary message body
Key assignments key field obtains the key assignments key of resource instances and stores, and according to the subscribing relationship list pre-setting, obtains at least one
Individual data variation consumption terminal, described intermediary message body is sent at least one described data variation consumption terminal；
Described data variation consumption terminal, for obtaining intermediary message body from Message Queuing system, from described intermediary message body
Message format format field obtains message format format, according to described message format format, described intermediary message body is entered
Row parsing, carries out data syn-chronization operation according to the intermediary message body after parsing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610803823.7A CN106339498A (en) | 2016-09-05 | 2016-09-05 | Method, device and system for synchronizing data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610803823.7A CN106339498A (en) | 2016-09-05 | 2016-09-05 | Method, device and system for synchronizing data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106339498A true CN106339498A (en) | 2017-01-18 |
Family
ID=57823738
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610803823.7A Pending CN106339498A (en) | 2016-09-05 | 2016-09-05 | Method, device and system for synchronizing data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106339498A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107122497A (en) * | 2017-05-25 | 2017-09-01 | 北京微影时代科技有限公司 | Data processing method, device, electronic equipment and computer-readable recording medium |
| CN107888660A (en) * | 2017-10-13 | 2018-04-06 | 杭州朗和科技有限公司 | Cloud service resource allocation method, medium, device and computing device |
| CN108121757A (en) * | 2017-11-10 | 2018-06-05 | 广州优视网络科技有限公司 | A kind of method of data synchronization, device, system, computing device and storage medium |
| CN108647237A (en) * | 2018-03-30 | 2018-10-12 | 厦门海迈科技股份有限公司 | Method of data synchronization between isomeric relationship type database |
| CN109962957A (en) * | 2017-12-26 | 2019-07-02 | 珠海全志科技股份有限公司 | A kind of method of data synchronization and device of multizone service mostly living |
| CN110069487A (en) * | 2017-09-28 | 2019-07-30 | 北京国双科技有限公司 | A kind of data processing method, apparatus and system |
| CN111241044A (en) * | 2020-01-08 | 2020-06-05 | 中国联合网络通信集团有限公司 | Method, device and equipment for building heterogeneous database and readable storage medium |
| CN111460034A (en) * | 2020-03-25 | 2020-07-28 | 聚好看科技股份有限公司 | Database bidirectional synchronization method, synchronization unit and system |
| CN112799859A (en) * | 2021-01-26 | 2021-05-14 | 奇秦科技(北京)股份有限公司 | Data interaction method of hybrid cloud |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102495910A (en) * | 2011-12-28 | 2012-06-13 | 畅捷通信息技术股份有限公司 | Device and method for data timing synchronization of heterogeneous system |
| CN102542007A (en) * | 2011-12-13 | 2012-07-04 | 中国电子科技集团公司第十五研究所 | Method and system for synchronization of relational databases |
| CN103793749A (en) * | 2014-02-27 | 2014-05-14 | 四川物联恒安安全技术研究有限公司 | Safety production comprehensive supervisory platform data transmission method |
| US20150012486A1 (en) * | 2012-10-04 | 2015-01-08 | Oracle International Company | Efficient Pushdown Of Joins In A Heterogeneous Database System Involving A Large-Scale Low-Power Cluster |
| CN104573056A (en) * | 2015-01-22 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Database large data volume online migration method based on oracle |
-
2016
- 2016-09-05 CN CN201610803823.7A patent/CN106339498A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102542007A (en) * | 2011-12-13 | 2012-07-04 | 中国电子科技集团公司第十五研究所 | Method and system for synchronization of relational databases |
| CN102495910A (en) * | 2011-12-28 | 2012-06-13 | 畅捷通信息技术股份有限公司 | Device and method for data timing synchronization of heterogeneous system |
| US20150012486A1 (en) * | 2012-10-04 | 2015-01-08 | Oracle International Company | Efficient Pushdown Of Joins In A Heterogeneous Database System Involving A Large-Scale Low-Power Cluster |
| CN103793749A (en) * | 2014-02-27 | 2014-05-14 | 四川物联恒安安全技术研究有限公司 | Safety production comprehensive supervisory platform data transmission method |
| CN104573056A (en) * | 2015-01-22 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Database large data volume online migration method based on oracle |
Non-Patent Citations (1)
| Title |
|---|
| 王晓瑞等: "一种异构数据库间数据同步模型的研究", 《计算机时代》 * |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107122497A (en) * | 2017-05-25 | 2017-09-01 | 北京微影时代科技有限公司 | Data processing method, device, electronic equipment and computer-readable recording medium |
| CN110069487A (en) * | 2017-09-28 | 2019-07-30 | 北京国双科技有限公司 | A kind of data processing method, apparatus and system |
| CN107888660A (en) * | 2017-10-13 | 2018-04-06 | 杭州朗和科技有限公司 | Cloud service resource allocation method, medium, device and computing device |
| CN108121757A (en) * | 2017-11-10 | 2018-06-05 | 广州优视网络科技有限公司 | A kind of method of data synchronization, device, system, computing device and storage medium |
| CN109962957B (en) * | 2017-12-26 | 2022-04-05 | 珠海全志科技股份有限公司 | Data synchronization method and device for multi-region multi-active service |
| CN109962957A (en) * | 2017-12-26 | 2019-07-02 | 珠海全志科技股份有限公司 | A kind of method of data synchronization and device of multizone service mostly living |
| CN108647237A (en) * | 2018-03-30 | 2018-10-12 | 厦门海迈科技股份有限公司 | Method of data synchronization between isomeric relationship type database |
| CN111241044A (en) * | 2020-01-08 | 2020-06-05 | 中国联合网络通信集团有限公司 | Method, device and equipment for building heterogeneous database and readable storage medium |
| CN111241044B (en) * | 2020-01-08 | 2023-09-19 | 中国联合网络通信集团有限公司 | Method, device, equipment and readable storage medium for constructing heterogeneous database |
| CN111460034A (en) * | 2020-03-25 | 2020-07-28 | 聚好看科技股份有限公司 | Database bidirectional synchronization method, synchronization unit and system |
| CN111460034B (en) * | 2020-03-25 | 2024-02-23 | 聚好看科技股份有限公司 | Bidirectional database synchronization method, synchronization unit and system |
| CN112799859A (en) * | 2021-01-26 | 2021-05-14 | 奇秦科技(北京)股份有限公司 | Data interaction method of hybrid cloud |
| CN112799859B (en) * | 2021-01-26 | 2021-09-07 | 奇秦科技(北京)股份有限公司 | Data interaction method of hybrid cloud |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106339498A (en) | Method, device and system for synchronizing data | |
| US8676863B1 (en) | Maintaining a relational database and its schema in response to a stream of XML messages based on one or more arbitrary and evolving XML schemas | |
| US20050114394A1 (en) | Mapping XML schema components to qualified Java components | |
| CN103294652B (en) | A kind of data transfer device and system | |
| CN101295311B (en) | Semantic matching algorithm of large scale issuance and subscription system | |
| CN106599104A (en) | Mass data association method based on redis cluster | |
| US9317518B2 (en) | Data synchronization | |
| CN104765840A (en) | Big data distributed storage method and device | |
| CN102982010A (en) | Method and device for abstracting document structure | |
| CN104794190A (en) | Method and device for effectively storing big data | |
| CN100498787C (en) | Report generating method, equipment and system | |
| CN104750855A (en) | Method and device for optimizing big data storage | |
| CN102073662B (en) | Method and system for analyzing and creating XML (Extensible Markup Language) data | |
| CN110807038A (en) | CMDB information full-text retrieval method based on elastic search | |
| CN103164476A (en) | Execution method and execution device of applying metadata to describe files in business intelligence (BI) | |
| CN101799890B (en) | Certificate data processing method and system | |
| CN105912723A (en) | Storage method of custom field | |
| CN103473106B (en) | Method and system for generating page | |
| CN101826087B (en) | Configuration device and method of coding information data | |
| KR101955376B1 (en) | Processing method for a relational query in distributed stream processing engine based on shared-nothing architecture, recording medium and device for performing the method | |
| CN103744991A (en) | Method for XML-based data transmission between SAP systems | |
| CN101516086B (en) | Service matching method for mobile communication | |
| CN102486731A (en) | Method, device and system for enhancing visualization of software call stack of software | |
| CN105224319B (en) | The method for realizing XBRL instance document previews based on dom4j | |
| CN105787013B (en) | A kind of the typonym distribution method and system of isomeric data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170118 |
|
| RJ01 | Rejection of invention patent application after publication |