CN101640587B - Data synchronization method and device - Google Patents

Abstract

The invention provides a data synchronization method, which comprises the following steps: acquiring trigger of a service layer for synchronizing data; and synchronizing the data to be synchronized to the physical database according to the trigger, and synchronizing the data synchronized to the physical database to the memory database. The invention also provides two data synchronization devices. In the invention, the service layer sends a trigger to respectively synchronize the data to the physical database and the memory database, and because the data synchronized to the physical database is synchronized to the memory database, the defect that the contents of the synchronized data are inconsistent because the service layer respectively synchronizes the data to the physical database and the memory database is avoided. Therefore, the embodiment of the invention can keep the integrity of the semantics when synchronizing the data to the physical database and the in-memory database.

Description

Data synchronization method and device

technical field

The invention relates to data processing technology, in particular to data synchronization technology.

Background technique

Some business systems including the business layer, physical database and memory database often need to write data to the physical database and memory database at the same time when performing business operations. For the convenience of description, this process is generally called data synchronization. For example, when an Online Charging System (OCS, Online Charging System) performs business operations, it needs to write data to physical storage (usually a physical database) and memory storage (usually a memory database) at the same time, such as writing user information, account Information, etc., for the convenience of description, this process is generally called data synchronization.

An existing data synchronization method is that in the business layer (the layer that processes business logic), data needs to be synchronized to a physical database and an in-memory database respectively. That is, in order to synchronize the data of the same content to the physical database and the in-memory database respectively, two operations need to be performed at the business layer: one operation is to synchronize the data of the same content to the physical database; the other operation is to synchronize the data of the same content Data is synchronized to an in-memory database.

In the process of implementing the present invention, the inventor found that in the above data synchronization method, since the data needs to be synchronized to the physical database and the memory database respectively at the business layer, the integrity of the semantics is easily damaged. For example, due to the relatively large amount of data being operated, misoperation, etc., the data synchronized to the physical database and the in-memory database may not be consistent in content.

Contents of the invention

The embodiments of the present invention provide a data synchronization method and device for maintaining semantic integrity when synchronizing data to a physical database and a memory database.

A data synchronization method, applicable to business systems including a business layer, a physical database and an in-memory database, comprising: obtaining a trigger for synchronizing data in the business layer; according to the trigger, synchronizing the data to be synchronized to the physical database, and synchronizing The data sent to the physical database is synchronized to the memory database.

A data synchronization device, suitable for a business system including a business layer, a physical database, and an in-memory database, comprising: a trigger obtaining unit for obtaining a trigger for synchronizing data at the business layer; a data synchronization unit for obtaining a unit according to the trigger The obtained trigger synchronizes the data that needs to be synchronized to the physical database, and synchronizes the data synchronized to the physical database to the memory database.

A data synchronization device, comprising: a business component unit, a data operation component unit, a data type converter, a data synchronization context unit, a synchronization interceptor, and a remote synchronization component unit; the business component unit is used to trigger the synchronization needs of the data operation component unit Synchronized data; the data operation component unit is used to generate a physical database operation instruction including the data to be synchronized according to the trigger of the business component unit, send the physical database operation instruction to the physical database, and extract the memory database operation The necessary information, the information necessary for the operation of the memory database is sent to the data type converter, the information necessary for the operation of the memory database includes the data synchronized to the physical database; the data type converter is used to The information necessary for the memory database operation provided by the data operation component unit, assemble the memory database operation instruction, and send the memory database operation instruction to the data synchronization context unit, wherein, if the data type of the physical database is the same as that of the memory database If the data types are inconsistent, then the data synchronized to the physical database included in the information necessary for the operation of the memory database is converted into data of the memory database type, and the memory database operation instruction includes the data of the memory database type; The data synchronization context unit is used to store the instructions assembled by the data type converter; the synchronization interceptor is used to actively obtain all instructions stored by the data synchronization context unit or all instructions about a business from the data synchronization context unit , and send all the instructions or all instructions about a business to the remote synchronization component unit; the remote synchronization component unit is used to send all the instructions provided by the synchronization interceptor or all instructions about a business Remotely sent to the memory database.

In the embodiment of the present invention, when the business layer sends a trigger, the data can be synchronized to the physical database and the memory database. The defect that the content of the synchronized data is inconsistent due to the synchronization of data between the physical database and the memory database. It can be seen that the embodiment of the present invention can maintain semantic integrity when synchronizing data to a physical database and an in-memory database.

Description of drawings

FIG. 1 is a flowchart of a data synchronization method according to an embodiment of the present invention;

2 is a schematic structural diagram of a data synchronization device according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of another data synchronization device according to an embodiment of the present invention;

FIG. 4 is a flowchart of a data synchronization method based on FIG. 3 according to an embodiment of the present invention.

Detailed ways

Firstly, the data synchronization method according to the embodiment of the present invention will be described with reference to FIG. 1 . The data synchronization method in the embodiment of the present invention is applicable to a business system including a business layer, a physical database and an in-memory database, such as an online charging system. As shown in Figure 1, including:

Step S101: Obtain a trigger that the business layer needs to synchronize data.

Step S102: According to the trigger, synchronize the data to be synchronized to the physical database, and synchronize the data synchronized to the physical database to the memory database.

Data that needs to be synchronized can be obtained in various ways. For example, the data that needs to be synchronized can be carried in the obtained trigger, so that when the trigger is obtained, the data that needs to be synchronized is also obtained. For another example, when obtaining the trigger that the business layer needs to synchronize data, the data that needs to be synchronized provided by the business layer may also be obtained, that is, the trigger and the data that needs to be synchronized are obtained separately.

When synchronizing the data to be synchronized to the physical database, a physical database operation instruction can be generated according to the data to be synchronized, and the physical database operation instruction can be sent to the physical database.

When synchronizing the data to be synchronized to the physical database, the data to be synchronized can be directly or indirectly operated on the physical database through the Application Programming Interface (API, Application Programming Interface) to synchronize the data to be synchronized to the physical database.

When synchronizing the data synchronized to the physical database to the memory database, the information necessary for the operation of the memory database can be extracted first; if the data type of the physical database is inconsistent with the data type of the memory database, then the information necessary for the operation of the memory database will be included The data of the physical database type is converted into the data of the memory database type; after that, according to the data of the memory database type and other information in the information necessary for the operation of the memory database, the memory database operation instruction is assembled, wherein, one or more An in-memory database operation instruction corresponds to an operation of a business; finally, the in-memory database operation instructions corresponding to all operations of a business are sent to the in-memory database together.

After the in-memory database operation instructions are assembled, the in-memory database operation instructions can also be stored in the data synchronization context, and when the in-memory database operation instructions corresponding to all operations of a business are sent to the in-memory database together, the synchronous interceptor with interception function can actively Obtain the in-memory database operation instructions corresponding to all operations of a business from the data synchronization context, and send the in-memory database operation instructions corresponding to all operations of a business to the in-memory database through the remote synchronization component by the synchronous interceptor with interception function , wherein the remote synchronization component provides the function of remote accessing the memory database.

After extracting the information necessary for in-memory database operations, the information necessary for in-memory database operations can also be stored in the data synchronization context, and then the synchronization interceptor with the interception function can actively obtain all operations corresponding to a business from the data synchronization context The information necessary for the operation of the memory database. It should be noted that the data of the physical database type in the information necessary for the operation of the memory database is converted into the data of the memory database type, the operation instructions of the memory database are assembled, and all operations of a business The corresponding in-memory database operation instructions can be sent to the in-memory database together by the synchronous interceptor.

The aforementioned data synchronization context may be a storage variable, a data storage queue or a shared area bound to information necessary for a single transaction.

The above-mentioned remote synchronization component can be a remote operation API of the memory database, and the above-mentioned remote synchronization component can also remotely access the memory database through distributed object processing technology or network communication technology.

In addition, if the data synchronized to the physical database fails to be synchronized to the memory database, the physical database may be notified to perform a transaction rollback operation.

The above-mentioned data synchronization method can be implemented by devices in various forms, and these devices are suitable for business systems including business layers, physical databases and memory databases, such as online billing systems, and one of the data synchronization devices is shown in Figure 2. Including: a trigger obtaining unit 201, used to obtain the trigger that needs to synchronize data in the business layer; a data synchronization unit 202, used to synchronize the data that needs to be synchronized to the physical database according to the trigger obtained by the trigger obtaining unit, and synchronize to the physical database. The data of the database is synchronized to the memory database.

The data that needs to be synchronized can be carried in the trigger obtained by the trigger obtaining unit 201, so that when the trigger obtaining unit 201 obtains the trigger, the data that needs to be synchronized is also obtained. In addition, when the trigger obtaining unit 201 obtains the trigger that the service layer needs to synchronize data, it can also obtain the data that needs to be synchronized provided by the service layer, that is, the trigger and the data that need to be synchronized are obtained separately by the trigger obtaining unit 201 .

The data synchronization unit 202 may include: an instruction generation unit 2021, configured to generate a physical database operation instruction according to the data to be synchronized; a first instruction issuing unit 2022, configured to send the physical database operation instruction generated by the instruction generation unit 2021 to the physical database .

When the data synchronization unit 202 synchronizes the data to be synchronized to the physical database, it may directly or indirectly use the physical database operation API to synchronize the data to be synchronized to the physical database.

The data synchronization unit 202 may include: an information extraction unit 2023, which is used to extract information necessary for the operation of the memory database; a data type conversion unit 2024, which is used to convert the information extraction unit to the data type if the data type of the physical database is inconsistent with the data type of the memory database. The data of the physical database type in the information necessary for the operation of the memory database extracted in 2023 is converted into the data of the memory database type; the instruction assembly unit 2025 is used for converting the data of the memory database type according to the data type conversion unit 2024 and the information extraction unit 2023 Other information in the extracted information necessary for the operation of the memory database is assembled into an operation instruction of the memory database, wherein one or more operation instructions of the memory database correspond to an operation of a business; the second instruction issuing unit 2026 is used to assemble the instruction into the unit In-memory database operation instructions corresponding to all operations of a business assembled in 2025 are sent to the in-memory database together.

The above-mentioned data synchronization device can also include an instruction storage unit 203, which is used to store the memory database operation instructions assembled by the instruction assembly unit 2025 into the data synchronization context; the second instruction issuing unit 2026 can be a synchronization interceptor with an interception function, and the synchronization The interceptor can actively obtain the in-memory database operation instructions corresponding to all operations of a business from the data synchronization context.

The above-mentioned data synchronization device may also include: an information storage unit 204, which is used to store the information necessary for the operation of the memory database extracted by the information extraction unit 2023 into the data synchronization context; a synchronization interceptor 205 with an interception function, which is used to actively synchronize data from In the context, all the operations of a business correspond to the information necessary for the memory database operation; and the data type conversion unit 2024 , the instruction assembly unit 2025 and the second instruction issuing unit 2026 can be integrated in the synchronization interceptor 205 .

In addition to the above-mentioned method embodiment and device embodiment, the embodiment of the present invention also provides a data synchronization device as shown in Figure 3, the data synchronization device includes: a business component (Business Component) unit 301, a data manipulation component (Data Manipulation Component) ) unit 302, data type converter 303, data synchronization context unit 304, synchronization interceptor 305, and remote synchronization component unit 306.

The business component unit 301 mainly deals with business logic, especially business logic that needs to synchronize data, such as account opening, product order, product change and so on. Specifically, when the service component unit 301 is to realize a certain service, it can notify the data operation component unit 302 of the need to realize the service, or in other words, trigger the data operation component unit 302 to synchronize the data to be synchronized. The business component unit 301 may include at least one business component.

The data operation component unit 302 is mainly used to be responsible for specific data operations according to the trigger of the business component unit 301 . For example, data can be added to the physical database 100 directly or indirectly through the physical database operation API. The data operation component unit 302 may include at least one data operation component.

The data operation component unit 302 can encapsulate specific data operations. For example, for the operation of adding users, it can be encapsulated as an API provided by the data operation component. The business component can realize the operation of adding users through this API without concern Whether the data is synchronized to the physical database 100 or the in-memory database 200 .

In addition, when the data operation component unit 302 synchronizes data to the physical database 100 , it may generate a physical database operation instruction including the data to be synchronized, and then send the generated physical database operation instruction to the physical database 100 . Instructions may include actions for operations and associated data. Taking account opening as an example, the instructions generated by the data operation component unit 302 for the physical database 100 may include actions related to account opening and related data. One business can correspond to multiple operations. Taking account opening as an example, it can correspond to three operations: adding users, adding customers, and adding accounts. For this, the data operation component unit 302 can generate one or more instructions corresponding to each operation , so, for the account opening business, the data operation component unit 302 can generate at least three instructions.

In addition, the data operation component unit 302 can also extract the information necessary for the operation of the in-memory database, and send the information necessary for the operation of the in-memory database to the data type converter 303 . The information necessary for the operation of the in-memory database may come from the notification sent by the business component unit 301 to the data operation component unit 302 , or from the data synchronized by the data operation component unit 302 to the physical database 100 . Obviously, in order to ensure that the data synchronized to the physical database 100 is consistent with the data synchronized to the internal database 200 , the information necessary for the operation of the in-memory database includes the data synchronized to the physical database 100 .

The data type converter 303 is mainly used to assemble the memory database operation instruction according to the information necessary for the memory database operation provided by the data operation component unit 302 , and send the memory database operation instruction to the data synchronization context unit 304 .

Wherein, if the data type of the physical database 100 is inconsistent with the data type of the in-memory database 200, the data synchronized to the physical database 100 included in the information necessary for the operation of the in-memory database may be converted into the data of the in-memory database type, said The in-memory database operation instruction includes data of the in-memory database type.

Generally speaking, the data type of the physical database is inconsistent with the data type of the memory database. Therefore, if the data provided by the physical database 100 is directly or indirectly provided to the memory database 200, the data of the type of the physical database 100 ( It may be the data with specific content in the information necessary for the operation of the memory database) into the data of the memory database 200 type, and then assemble the data of the memory database 200 type into the memory database operation instruction. Of course, if the information necessary for the operation of the memory database includes not only data with specific content, but also some necessary operation instructions. Then the data type converter 303 needs to assemble the operation instruction of the memory database according to the operation instruction in addition to the above-mentioned data of the type of the memory database 200 .

Optionally, the data type conversion can also be completed in the remote synchronization component unit 306 , and can also be completed in the memory database 200 . It should be noted that although in general, the data type of the physical database is inconsistent with the data type of the memory database, in some cases, the data type of the physical database and the data type of the memory database may still be consistent. For this, When the data operation component unit 302 sends the data of the physical database 100 type to the data type converter 303, the data type converter 303 does not need to convert the data type, but directly assembles the memory database operation instruction according to the data of the physical database 100 type, and Send the assembled instructions to the data synchronization context unit 304 .

The data synchronization context unit 304 is mainly used to store instructions assembled by the data type converter 303 . A data synchronization context may refer to a data storage bound to information necessary for a single transaction, such as a storage variable, a data storage queue or a shared area. In addition, the data synchronization context can be shared, and multiple data operation components can share the data synchronization context.

The synchronization interceptor 305 is mainly used to actively obtain all instructions stored in the data synchronization context unit 304 or all instructions related to a service from the data synchronization context unit 304 . Specifically, after all the instructions are acquired, all the instructions may be packaged and then sent to the remote synchronization component unit 306 . A typical feature of the synchronous interceptor 305 is that it is transparent to business components and has nothing to do with specific business semantics.

The remote synchronization component unit 306 provides the ability to remotely access the in-memory database 200 . Specifically, after obtaining the instruction provided by the synchronization interceptor 305 , the remote synchronization component unit 306 can send the instruction to the in-memory database 200 , so that the data that needs to be synchronized to the in-memory database 200 is synchronized to the in-memory database 200 .

In a specific implementation, the remote synchronization component unit 306 includes at least one remote synchronization component. The remote synchronization component can be a remote operation API of an in-memory database. The remote synchronization component unit 306 can realize remote operation of the in-memory database through distributed object processing technology or network communication technology. 200, for example, send the instruction to the memory database 200 through the distributed object processing technology or the network communication technology.

FIG. 4 is a flowchart of a data synchronization method based on the data synchronization device in FIG. 3 . As shown in Figure 4, including:

Step S401: The business component unit 301 calls the data operation component unit 302 to complete operations such as adding, modifying and deleting data.

Step S402: The data operation component unit 302 generates a physical database operation instruction to complete the operation on the physical database 100. The physical database operation instruction can be realized by Structured Query Language (SQL, Structured Query Language).

Step S403: the data operation component unit 302 extracts the information necessary for the operation of the memory database, and then transmits the necessary information to the data type converter 303 .

Step S404: The data type converter 303 assembles the in-memory database operation instruction according to the necessary information.

Step S405: the data type converter 303 sends the assembled in-memory database operation instruction to the data synchronization context unit 304.

It should be noted here that since the data synchronization context unit 304 can store the memory database operation instructions involved in all operations of a business, if a complete business process involves multiple operations, for example, the account opening business involves adding users, adding customers, and For three operations such as adding an account, it is necessary to repeat steps S402-S405, so as to realize that the memory database operation instructions involved in all operations are stored in the data synchronization context unit 304.

In this regard, after step S405, step S406 is also included: judging whether it is necessary to return to step S402, if yes, return to step S402, otherwise go to step S407.

Step S407: Synchronization interceptor 305 actively obtains all in-memory database operation instructions stored in data synchronization context unit 304 or all in-memory database operation instructions of a business from data synchronization context unit 304, and assembles all in-memory database operation instructions of a business into a new command, and then send the new command to the remote synchronization component unit 306.

Step S408 : the remote synchronization component unit 306 sends the new instruction to the in-memory database 200 .

Step S409: The in-memory database completes data operations in batches according to the new instructions.

Step S410: batch update is performed in one transaction of the in-memory database 200, if successful, go to step S413, otherwise, go to step S411.

Step S411 : the in-memory database 200 completes transaction rollback and notifies the synchronization interceptor 305 through the remote synchronization component unit 306 .

Step S412: the synchronous interceptor 305 notifies the physical database 100 (specifically, the transaction manager of the physical data operation) that the transaction is abnormal, and completes the rollback of the physical data.

Step S413: the business process ends.

It should be noted that the apparatus shown in FIG. 3 and the method shown in FIG. 4 can be applied to an online charging system. The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without any creative effort.

Through the above description of the implementations, those skilled in the art can clearly understand that each implementation can be implemented by means of software plus a necessary general hardware platform, and of course also by hardware. Based on this understanding, the essence of the above technical solution or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products can be stored in computer-readable storage media, such as ROM/RAM, magnetic discs, optical discs, etc., including several instructions to make a computer device (which may be a personal computer, server, or network device, etc.) execute the methods described in various embodiments or some parts of the embodiments.

In order to make those skilled in the art understand the embodiment of the present invention more clearly, the following takes a typical account opening service in an online billing system as an example to describe the working process of the data synchronization method or the data synchronization device according to the embodiment of the present invention in detail.

Assume that in the process of opening an account, operations of adding users (addSubscriber), adding customers (addCustomer) and adding accounts (addAccount) are required, that is, the so-called three-account information increase. The information of the three households must be added to both the physical database and the memory database, that is, the data of the account opening business needs to be synchronized to the physical database and the memory database.

The data synchronization method for account opening business is as follows:

The business component (that is, the account opening logic) first calls the add user API of the data operation component, and the account opening logic can be encapsulated into a class, such as SubscriberService, where the newSubscriber method provides the account opening logic. newSubscriber calls the addSubscriber method of the data operation component.

The addSubscriber method of the data operation component generates physical database operation instructions. Here, it is assumed that SQL statements similar to the following are directly generated:

insert into subscriber values(…)

In this way, user information is added to the physical database.

The data operation component extracts the information necessary for the operation of the memory database. Here, it is assumed that the table data fields of the memory database are the same as those of the physical database, but the data format is slightly different. In-memory database is an integer type. The data operation component sends the information necessary for the operation of the memory database to the data type converter.

The data type converter is responsible for converting the data of the physical database type into the data of the memory database type, and assembling the operation instructions of the memory database according to the data of the memory database type. For this embodiment, the data type converter converts the effective time of the user into an integer value relative to Greenwich Mean Time, and after sorting out, an in-memory database operation instruction is generated. In this embodiment, the in-memory database operation instruction and the physical database operation instruction Basically equivalent, namely:

insert into subscriber values(…)

However, some data values of the in-memory database operation instructions are different from those of the physical database operation instructions, such as the effective time here.

The data type converter sends the memory database operation instruction to the data synchronization context. In this embodiment, the realization of the data synchronization context is a thread-bound variable in Java. Examples are as follows:

ThreadLocal requestContextHolder = new InheritableThreadLocal();

Wherein, the instruction issued to the memory is stored in the thread variable.

For the account opening business, three operation data are required, that is, adding users, adding customers, and adding accounts. For this, the above process needs to be executed three times until the data type converter synchronizes all the memory database operation instructions corresponding to adding users, adding customers, and adding accounts. Until the data synchronization context.

In this embodiment, an aspect-oriented programming (AOP, Aspect Oriented Programming) method is used to add a synchronous interceptor to the API corresponding to the account opening logic. The synchronous interceptor only needs to implement a specific interface and configure it in AOP. Taking Spring as an example, you can configure it as follows:

<aop:config>

<aop:pointcut id="syncOperation"

expression="execution(*...(..))"/>

<aop:advisor advice-ref="syncAdvice"

pointcut-ref="syncOperation"/>

</aop:config>

<bean id="syncAdvice" class="..."/>

After the data type converter synchronizes all the in-memory database operation instructions corresponding to the three operations to the data synchronization context, the synchronization interceptor can actively obtain the in-memory database operation instructions corresponding to the three operations from the data synchronization context, and convert these instructions assembled as a new instruction.

The synchronization interceptor sends the assembled new instructions to the memory database through the remote synchronization component, wherein the remote synchronization component can use the socket mode to send the SQL instruction of the string.

The memory database completes the operations of adding users, adding customers, and adding accounts in batches in a memory transaction according to SQL instructions. The batch update is performed in one transaction of the memory database, so far, the data synchronization process of the account opening business is over.

In the embodiment of the present invention, the physical data operation and the memory database operation are unified, thereby maintaining the integrity of the business semantics. For the business, data persistence is centralized to provide consistent semantics externally.

In the embodiment of the present invention, the transaction of the physical database adopts unified control, and the memory is synchronized once at the end of the business, so that when the memory data processing fails, the physical database can be notified to roll back the transaction. In addition, the memory operation can also be controlled within a transaction, thus realizing the control of the transaction relatively simply.

In the embodiment of the present invention, the synchronization memory instructions generated in the business process can be collected and sent through the data synchronization context, so that batch processing can be performed, unnecessary remote interaction is reduced, and the performance of data synchronization is improved.

In the embodiment of the present invention, the data synchronization action can be hidden from the business through the synchronization interceptor, thereby providing the ability of a single interface for data operation, reducing the possibility of errors, and facilitating system development.

The above is only a preferred embodiment of the present invention, it should be pointed out that for those of ordinary skill in the art, without departing from the principle of the present invention, some improvements and modifications can also be made, and these improvements and modifications should also be It is regarded as the protection scope of the present invention.

Claims (18)

1. a method of data synchronization is characterized in that, is applicable to the operation system that comprises operation layer, physical database and memory database, comprising:

Obtaining operation layer needs the triggering of synchrodata;

According to said triggering, will need data in synchronization to be synchronized to physical database, and the data sync that will be synchronized to physical database is to memory database; If the data sync that will be synchronized to physical database to the memory database failure, then notifies physical database to carry out the transaction rollback operation;

The said data sync that will be synchronized to physical database specifically comprises to memory database:

Extract the memory database operation information necessary;

If the data type of the data type of physical database and memory database is inconsistent, then the data transaction with the physical database type in the said memory database operation information necessary is the data of memory database type;

According to the data of said memory database type and other information in the said memory database operation information necessary, the instruction of assembly unit memory database operation, wherein, an operation of the corresponding business of one or more memory database operation instructions;

Memory database is together issued in the memory database operation instruction that all operations of a business is corresponding respectively.

2. method of data synchronization as claimed in claim 1 is characterized in that, the said needs in the triggering that data in synchronization is carried on acquisition, when perhaps obtaining operation layer and needing the triggering of synchrodata, also obtains the said data in synchronization that needs that operation layer provides.

3. according to claim 1 or claim 2 method of data synchronization is characterized in that, will need data in synchronization to be synchronized to physical database and specifically comprise:

Data in synchronization generates the physics database operating instruction as required, and the physical database operational order is issued physical database.

4. according to claim 1 or claim 2 method of data synchronization; It is characterized in that; To need data in synchronization to be synchronized to physical database is specially: directly or indirectly through physical database operational applications DLL API, will need data in synchronization to be synchronized to physical database.

5. method of data synchronization as claimed in claim 1; It is characterized in that; After the instruction of assembly unit memory database operation; Also comprise: with the memory database operation instruction storage to the data sync context; The memory database operation instruction that all operations of a business is corresponding is respectively together issued memory database and is specifically comprised: the corresponding respectively memory database operation instruction of all operations of initiatively from the data sync context, being obtained a business by the synchronous intercepting device with interception function; And together issue memory database through the remote synchronization assembly by the memory database operation instruction that all operations of a business is corresponding respectively of the synchronous intercepting device with interception function, wherein, the remote synchronization assembly provides the function of remote access memory database.

6. method of data synchronization as claimed in claim 1 is characterized in that, after the extraction memory database operation information necessary, also comprises:

Store the memory database operation information necessary into the data sync context;

Initiatively from the data sync context, obtain the corresponding respectively memory database operation information necessary of all operations of a business by synchronous intercepting device with interception function; And,

With the data transaction of the physical database type in the said memory database operation information necessary is that data, the instruction of assembly unit memory database operation and the memory database operation instruction that all operations of a business is corresponding respectively of memory database type together issued memory database and all accomplished by the synchronous intercepting device.

7. like claim 5 or 6 described method of data synchronization, it is characterized in that said data sync context is storage of variables, data queue memory or the shared region of binding with the professional information necessary of single.

8. method of data synchronization as claimed in claim 5 is characterized in that, the remote synchronization assembly is the remote operation API of memory database, perhaps through distribute objects treatment technology or network communications technology remote access memory database.

9. a data synchronization unit is characterized in that, is applicable to the operation system that comprises operation layer, physical database and memory database, comprising:

Trigger obtaining the unit, be used to obtain the triggering that operation layer needs synchrodata;

Data synchronisation unit is used for obtaining the triggering that the unit obtains according to said triggering, will need data in synchronization to be synchronized to physical database, and the data sync that will be synchronized to physical database is to memory database; If the data sync that will be synchronized to physical database to the memory database failure, then notifies physical database to carry out the transaction rollback operation;

Said data synchronisation unit comprises:

Information extraction unit is used to extract the memory database operation information necessary;

The data type conversion unit; If it is inconsistent to be used for the data type of data type and memory database of physical database, the data transaction of the physical database type in the memory database operation information necessary of then said information extraction unit being extracted is the data of memory database type;

Instruction assembly unit unit; Other information of the memory database operation information necessary that is used for extracting according to the data and the said information extraction unit of the memory database type of said data type conversion cell translation; The instruction of assembly unit memory database operation; Wherein, an operation of the corresponding business of one or more memory database operation instructions;

The second instruction issue unit is used for the memory database operation instruction that all operations of a business of said instruction assembly unit unit splicing is corresponding respectively and together issues memory database.

10. data synchronization unit as claimed in claim 9 is characterized in that, said data synchronisation unit also comprises:

The instruction generation unit is used for data in synchronization as required, generates the physics database operating instruction;

The first instruction issue unit is used for the physical database operational order that said instruction generation unit generates is issued physical database.

11. data synchronization unit as claimed in claim 9 is characterized in that, also comprises: the location of instruction is used for memory database operation instruction storage with said instruction assembly unit unit splicing to the data sync context; The said second instruction issue unit is the synchronous intercepting device with interception function, and said synchronous intercepting device initiatively obtains the corresponding respectively memory database operation instruction of all operations of a business from the data sync context.

12. data synchronization unit as claimed in claim 11 is characterized in that, also comprises:

Information memory cell is used for storing the memory database operation information necessary that said information extraction unit is extracted into the data sync context;

Synchronous intercepting device with interception function is used for a business is obtained in active from the data sync context the corresponding respectively memory database operation information necessary of all operations; And said data type conversion unit, instruction assembly unit unit and the second instruction issue unit are integrated in the said synchronous intercepting device.

13. a data synchronization unit is characterized in that, comprising: Service Component unit, data manipulation assembly unit, data type converter, data sync context unit, synchronous intercepting device and remote synchronization assembly unit;

Said Service Component unit is used for trigger data operating assembly units synchronization and needs data in synchronization;

Said data manipulation assembly unit is used for the triggering according to said Service Component unit; Generation comprises needs the physical database of data in synchronization operational order; Said physical database operational order is issued physical database; And extract the memory database operation information necessary, and said memory database operation information necessary is issued said data type converter, said memory database operation information necessary comprises the data of giving physical database synchronously;

Said data type converter is used for the memory database operation information necessary that provides according to said data manipulation assembly unit; The instruction of assembly unit memory database operation; And the instruction of said memory database operation issued said data sync context unit; Wherein, If the data type of the data type of physical database and memory database is inconsistent, be the data of memory database type also then with the synchronous data transaction that comprises in the said memory database operation information necessary to physical database, said memory database operation instruction comprises the data of said memory database type;

Said data sync context unit is used to store the instruction of said data type converter assembly unit;

Said synchronous intercepting device be used for initiatively obtain all instructions of said data sync context unit storage or about all instructions of a business from said data sync context unit, and issue said remote synchronization assembly unit with said all instructions or about all instructions of a business;

Said all instructions that said remote synchronization assembly unit is used for said synchronous intercepting device is provided or about the long-range memory database of issuing of all instructions of a business.

14. data synchronization unit as claimed in claim 13; It is characterized in that; Said data sync context unit comprises at least one data sync context, and a data synchronous context is storage of variables, data queue memory or the shared region of binding with the professional information necessary of single.

15. data synchronization unit as claimed in claim 14 is characterized in that, said data manipulation assembly unit comprises at least one data manipulation assembly, and a plurality of data manipulation assemblies are wherein shared a data synchronous context.

16. data synchronization unit as claimed in claim 13 is characterized in that, said Service Component unit comprises at least one Service Component, and said synchronous intercepting device is transparent to Service Component, and irrelevant with concrete business semantics.

17. data synchronization unit as claimed in claim 13 is characterized in that, said remote synchronization assembly unit comprises at least one remote synchronization assembly, and the remote synchronization assembly is the remote operation API of memory database.

18. data synchronization unit as claimed in claim 13; It is characterized in that; Said all instructions that said remote synchronization assembly unit provides said synchronous intercepting device or about all of a business instruction is long-range when issuing memory database, said all instructions that said synchronous intercepting device provided through distribute objects treatment technology or the network communications technology or about the long-range memory database of issuing of all instructions of a business.

Images