CN112685142A - Distributed data processing system - Google Patents
Distributed data processing system Download PDFInfo
- Publication number
- CN112685142A CN112685142A CN202011628305.9A CN202011628305A CN112685142A CN 112685142 A CN112685142 A CN 112685142A CN 202011628305 A CN202011628305 A CN 202011628305A CN 112685142 A CN112685142 A CN 112685142A
- Authority
- CN
- China
- Prior art keywords
- transaction
- data source
- heterogeneous data
- manager
- source node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The invention discloses a distributed data processing system. Wherein, this system includes: a plurality of heterogeneous data source nodes, each of the heterogeneous data source nodes comprising a plurality of different independent databases for storing business data; the local transaction managers correspond to the heterogeneous data source nodes one by one, and each local transaction manager is used for calling a corresponding thread to execute a transaction processing request in the heterogeneous data source node; a global transaction manager in communication with each of the local transaction managers, the global transaction manager configured to assign a corresponding thread to each of the local transaction managers. The invention solves the technical problem that the data in various data sources are difficult to operate when various data sources are introduced simultaneously in the prior art.
Description
Technical Field
The invention relates to the field of databases, in particular to a distributed data processing system.
Background
In the process of enterprise information construction and management, the development of computer network and database technology provides support for users to interactively access and process distributed heterogeneous data sources, and due to the influence of factors such as the stage, the technology, other economic factors and human factors of each business system construction and implementation of a data management system, a large amount of business data stored in different storage modes are accumulated in the development process of enterprises, the adopted data management systems are almost the same, and therefore the distributed heterogeneous multiple data sources of the enterprises are formed. However, the simultaneous introduction of multiple data sources makes it difficult to operate the multiple data sources, and thus the processing requirements of enterprises on heterogeneous data cannot be met.
Aiming at the problem that in the prior art, when a plurality of data sources are introduced simultaneously, data in the plurality of data sources are difficult to operate, an effective solution is not provided at present.
Disclosure of Invention
The embodiment of the invention provides a distributed data processing system, which at least solves the technical problem that data in multiple data sources are difficult to operate when the multiple data sources are introduced simultaneously in the prior art.
According to an aspect of an embodiment of the present invention, there is provided a distributed data processing system including: a plurality of heterogeneous data source nodes, each of the heterogeneous data source nodes comprising a plurality of different independent databases for storing business data; the local transaction managers correspond to the heterogeneous data source nodes one by one, and each local transaction manager is used for calling a corresponding thread to execute a transaction processing request in the heterogeneous data source node; a global transaction manager in communication with each of the local transaction managers, the global transaction manager configured to assign a corresponding thread to each of the local transaction managers.
Furthermore, after the connection information of the heterogeneous data source node is packaged, the identification is carried out through an annotation form, so as to determine the local transaction manager corresponding to the heterogeneous data source node.
Further, the global transaction manager includes a transaction scheduling manager, and when a first transaction request to a first heterogeneous data source node is received, a first local transaction manager corresponding to the first heterogeneous data source node sends a blocking message to the transaction scheduling manager, where the blocking message is used to block an operation object corresponding to the first transaction request; the transaction scheduling manager is further configured to detect whether there are other threads associated with the operand, and determine whether to terminate the other threads of the operand according to a detection result.
Further, the transaction scheduling manager includes a lock counter, and the lock counter is configured to record, when the first transaction processing request is received, the number of heterogeneous data source nodes that execute the first operation instruction, and determine that the heterogeneous data source node when the number is zero is the first heterogeneous data source node.
Further, in the event there are other threads associated with the operand, the transaction scheduling manager terminates the other threads associated with the operand.
Further, in the case that the operation object does not have other threads associated with the operation object, the transaction scheduling manager releases the blocking of the operation object and allocates transaction management resources to a second heterogeneous data source node.
Further, the transaction scheduling manager is further configured to send a transaction management end message to the first local transaction manager after terminating the other threads associated with the operand.
Further, the second heterogeneous data source node is configured to process another second transaction processing request using the transaction management resource, and store a processing result to a thread variable corresponding to the second heterogeneous data source node.
Further, the first heterogeneous data source node is further configured to execute the first transaction processing request, and store an execution result to a thread variable corresponding to the first heterogeneous data source node.
Further, the global transaction manager further includes a transaction recovery manager, and the transaction recovery manager is further configured to determine whether the heterogeneous data source node performs an error according to any one thread variable, control all the heterogeneous data source nodes to perform rollback under the condition that any one of the heterogeneous data source nodes performs the error, and control all the heterogeneous data source nodes to submit an execution result to the global transaction manager under the condition that none of the heterogeneous data source nodes performs the error.
In an embodiment of the present invention, a distributed data processing system in the foregoing embodiment of the present application includes a plurality of heterogeneous data source nodes, a plurality of local transaction managers, and a global transaction manager, where each of the heterogeneous data source nodes includes a plurality of different independent databases, and the databases are used to store service data; local transaction managers correspond to the heterogeneous data source nodes one by one, and each local transaction manager is used for calling a corresponding thread to execute a transaction processing request in the heterogeneous data source node; the global transaction manager is used for allocating corresponding threads for each local transaction manager. In big data applications, data is the basis for all systems. It is important to migrate or import application data to large data systems quickly and efficiently. The scheme can provide an automatic, efficient and convenient flow processing mode in the offline data storage direction. A new integration strategy is provided through a general framework of a distributed heterogeneous multi-data source, and the distributed heterogeneous multi-data source transaction processing flow is constructed to unify the access of distributed heterogeneous data source nodes to a database, so that the distributed heterogeneous multi-data source transaction has atomicity, consistency and integrity, and the technical problem that data in various data sources are difficult to operate when various data sources are introduced simultaneously in the prior art is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a schematic diagram of a distributed data processing system according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an alternative distributed data processing system in accordance with embodiments of the present invention;
FIG. 3 is a flow diagram of a distributed data processing system processing a transaction request according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In accordance with an embodiment of the present invention, there is provided an embodiment of a distributed data processing system, it being noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.
Fig. 1 is a schematic diagram of a distributed data processing system according to an embodiment of the present application, which is shown in connection with fig. 1 and includes:
a plurality of heterogeneous data source nodes 10, each of the heterogeneous data source nodes 10 including a plurality of different independent databases for storing service data;
a plurality of local transaction managers 20, where the local transaction managers 20 correspond to the heterogeneous data source nodes 10 one to one, and each local transaction manager 20 is configured to invoke a corresponding thread to execute a transaction processing request in the heterogeneous data source node 10;
a global transaction manager 30 in communication with each of the local transaction managers 20, the global transaction manager 30 configured to assign a corresponding thread to each of the local transaction managers 20.
Specifically, each heterogeneous data source node may be deployed on one server, each heterogeneous data source node includes multiple different and independent databases, that is, a distributed heterogeneous multi-source database, which may actually be used as a physical data storage layer, and forms heterogeneous storage for different types of service data, such as a distributed Hive database, a greenplus, a graph database neo4j, and the like, and then provides a uniform access interface to the outside.
Each time a new transaction is started (i.e., a new operation instruction is received) in the distributed heterogeneous multi-source database, the global transaction manager is required to schedule each data source of the local transaction manager proxy, and after the local transaction manager finishes processing the data source, the processing result is sent to the global transaction manager, and meanwhile, a corresponding function interface is provided for the global proxy to call.
The local transaction manager can be a local agent which is an interface between the database and the global transaction management and provides powerful support for the distributed heterogeneous multi-source database. For example, an ODBC generic interface may be employed for a file system, sql server database to implement a local proxy that supports data types common to the databases.
In order to support the Java environment and the transaction processing of the distributed heterogeneous multiple data sources of the application service, related adaptation interfaces can be added in JDBC (Java Database Connectivity, an application program interface in Java language used for specifying how a client program accesses a Database) extension specification, and a JDBC-compatible driver for distributed heterogeneous multiple data source access is defined to implement the related adaptation interfaces.
Fig. 2 is a schematic diagram of an alternative distributed data processing system according to an embodiment of the present invention, which is shown in fig. 2, and the distributed data processing system deploys a global transaction manager (GDTM) by Java applications on EJB (Enterprise Java Beans) servers, and provides an application server manager (GUI) as a man-machine interface for a user to operate. The application server manager may have performed resource scheduling in the resource adapter (which may be performed by a getResource function) through the data resource manager. The global transaction manager communicates with a plurality of local transaction managers (only two of which are shown in the figure) through a proxy server, the local transaction manager proxies a heterogeneous data source node, each heterogeneous data source node comprises a plurality of independent databases (Oracle, Mysql, Hive, greenplus), and the databases can service data from local transactions.
The distributed data processing system in the above embodiment of the present application includes a plurality of heterogeneous data source nodes, a plurality of local transaction managers, and a global transaction manager, where each of the heterogeneous data source nodes includes a plurality of different independent databases, and the databases are used to store service data; local transaction managers correspond to the heterogeneous data source nodes one by one, and each local transaction manager is used for calling a corresponding thread to execute a transaction processing request in the heterogeneous data source node; the global transaction manager is used for allocating corresponding threads for each local transaction manager. In big data applications, data is the basis for all systems. It is important to migrate or import application data to large data systems quickly and efficiently. The scheme can provide an automatic, efficient and convenient flow processing mode in the offline data storage direction. A new integration strategy is provided through a general framework of a distributed heterogeneous multi-data source, and the distributed heterogeneous multi-data source transaction processing flow is constructed to unify the access of distributed heterogeneous data source nodes to a database, so that the distributed heterogeneous multi-data source transaction has atomicity, consistency and integrity, and the technical problem that data in various data sources are difficult to operate when various data sources are introduced simultaneously in the prior art is solved.
As an alternative embodiment, after the connection information of the heterogeneous data source node is encapsulated, the connection information is identified in an annotation form, so as to determine the local transaction manager corresponding to the heterogeneous data source node.
In an optional embodiment, a transaction manager can be defined for each heterogeneous data source in a self-defined transaction annotation mode, the self-defined annotation is used on a method needing multiple data sources, the self-defined annotation is transmitted to the corresponding transaction manager, a method for capturing the self-defined annotation by a definition section is provided, and a data source object is obtained based on the transmitted data source name parameter.
As an alternative embodiment, the global transaction manager includes a transaction scheduling manager, and when receiving a first transaction request to a first heterogeneous data source node, a first local transaction manager corresponding to the first heterogeneous data source node sends a blocking message to the transaction scheduling manager, where the blocking message is used to block an operation object corresponding to the first transaction request; the transaction scheduling manager is further configured to detect whether there are other threads associated with the operand, and determine whether to terminate the other threads of the operand according to a detection result.
Specifically, the first transaction processing request may be: read instructions, write instructions, delete instructions, read instructions, and rollback instructions, among others. When a first transaction request to an operation object is received, it is necessary to determine whether or not there are any other threads associated with the operation object, thereby preventing data inconsistency and the like caused by simultaneous operations on the operation object by a plurality of threads. This step is performed by a transaction scheduling manager in the global transaction manager, which is responsible for invoking local transaction managers of different heterogeneous data source nodes.
In the process from the starting to the ending of the transaction method of one data source (a transaction processing request), all other used data sources are connected and stored into a cache; then, storing the execution result of the first self-defined transaction method in a variable of a thread; finally, other self-defined transaction methods are executed in sequence until the last transaction method. The transaction scheduling manager, upon receiving the lockout message, begins detecting whether there are other threads associated with the operand, and in the event that it is determined that there are other threads associated with the operand, may terminate the other threads associated with the operand and prevent data inconsistencies.
As an alternative embodiment, the transaction scheduling manager includes a lock counter, and the lock counter is configured to record, when the first transaction request is received, the number of heterogeneous data source nodes that execute the first operation instruction, and determine that the heterogeneous data source node when the number is zero is the first heterogeneous data source node.
Specifically, the lock counter may be used as a global transaction interceptor to perform a global transaction intercepting function. In the whole distributed heterogeneous multi-data source transaction processing process, method nesting for blocking transactions is involved, each database node enters the transaction method, other sub-transactions need to be intercepted after one sub-transaction is started, an initial value is set to be 0 by designing a lock counter, and the value of an actuator entering a lock is added with 1 each time one sub-transaction is executed.
try{
Lock execution count +1
}finally{
Minus 1
}
Based on the above scheme, it can be determined whether the transaction method is the first entry method, that is, the method for initiating the global transaction of the distributed heterogeneous multiple data sources starts, according to whether the lock counter is the initial value, and the first asynchronous data source node is the node where the global transaction starts.
As an alternative embodiment, the transaction scheduling manager terminates other threads associated with the operand in the event that there are other threads associated with the operand.
As an alternative embodiment, in the case of no other thread associated with the operand, the transaction scheduling manager releases the blocking of the operand and allocates transaction management resources to the second heterogeneous data source node.
The second heterogeneous data source node is a data source node other than the first heterogeneous data source node. In the absence of other threads associated with the operand, the transaction scheduling manager releases the blocking of the operand and allocates transaction management resources to the second heterogeneous data source node to enable the second heterogeneous data source node to execute other data processing instructions.
As an alternative embodiment, the transaction scheduling manager is further configured to send a transaction management end message to the first local transaction manager after terminating the other threads associated with the operand.
Specifically, the transaction management end message is used to inform the first heterogeneous data source node that the first data operation can be executed.
As an alternative embodiment, the second heterogeneous data source node is configured to process other second transaction processing requests using the transaction management resource, and store the processing result to the thread variable corresponding to the second heterogeneous data source node.
As an optional embodiment, the first heterogeneous data source node is further configured to execute the first transaction processing request, and store an execution result to a thread variable corresponding to the first heterogeneous data source node.
As an optional embodiment, the global transaction manager further includes a transaction recovery manager, and the transaction recovery manager is further configured to determine whether the heterogeneous data source node performs an error according to any thread variable, control all the heterogeneous data source nodes to perform rollback under the condition that any one of the heterogeneous data source nodes performs the error, and control all the heterogeneous data source nodes to submit an execution result to the global transaction manager under the condition that none of the heterogeneous data source nodes performs the error.
In particular, the transaction recovery manager provides a recovery scheme, such as a rollback scheme, for problems that arise during the processing of sub-transactions. The transaction recovery manager can check whether the thread variable has errors, so that whether any heterogeneous data source node executes errors is determined, whether the requirements of all rollback or all submission at the same time are met is further determined, and the consistency of all database transaction operations is ensured.
Fig. 3 is a flowchart of a distributed data processing system for processing a transaction request according to an embodiment of the present application, and a manner of processing a transaction request by a distributed data processing system is described below with reference to fig. 3.
The heterogeneous data source node 1 receives the transaction request, determines an operation object a corresponding to the transaction request, and informs a local transaction manager corresponding to the heterogeneous data source node 1. The local transaction manager sends a message to the global transaction manager that object a is blocked.
The other heterogeneous data source nodes 2 … … N form a cache queue, and the global transaction manager receives the message of the blocking object a through the transaction management message receiver and determines whether the thread related to the operation object a exists.
And under the condition that the judgment result is negative, releasing the blocking of the object A, and distributing the transaction management resources to other heterogeneous data source nodes. And other heterogeneous data source nodes execute other transaction processing by using the allocated transaction management resources, and store the transaction processing result to the thread variable after the transaction processing is finished.
And if so, submitting or terminating the transaction processing operation related to the object A, and sending a transaction management operation ending message to the local transaction manager corresponding to the heterogeneous data source node 1. After receiving the transaction management operation ending message, the local transaction manager locks the object A and processes the current transaction, and stores the processing result to the thread variable.
And the global transaction manager judges whether the thread variable has errors, performs rollback under the condition that the errors exist, simultaneously submits under the condition that the errors do not exist, returns the running state of the global distributed heterogeneous multi-data source transaction, and completes the response of the transaction processing request.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A distributed data processing system, comprising:
a plurality of heterogeneous data source nodes, each of the heterogeneous data source nodes comprising a plurality of different independent databases for storing business data;
the local transaction managers correspond to the heterogeneous data source nodes one by one, and each local transaction manager is used for calling a corresponding thread to execute a transaction processing request in the heterogeneous data source node;
a global transaction manager in communication with each of the local transaction managers, the global transaction manager configured to assign a corresponding thread to each of the local transaction managers.
2. The system of claim 1, wherein after the connection information of the heterogeneous data source nodes is encapsulated, the connection information is identified in a form of annotation to determine the local transaction manager corresponding to the heterogeneous data source nodes.
3. The system of claim 1, wherein the global transaction manager comprises a transaction scheduling manager, and when receiving a first transaction request to a first heterogeneous data source node, a first local transaction manager corresponding to the first heterogeneous data source node sends a blocking message to the transaction scheduling manager, and the blocking message is used for blocking an operation object corresponding to the first transaction request;
the transaction scheduling manager is further configured to detect whether there are other threads associated with the operand, and determine whether to terminate the other threads of the operand according to a detection result.
4. The system of claim 3, wherein the transaction scheduling manager comprises a lock counter configured to record a number of heterogeneous data source nodes executing the first transaction request when the first transaction request is received, and to determine the heterogeneous data source nodes that are the first heterogeneous data source node when the number is zero.
5. The system of claim 3, wherein the transaction scheduling manager terminates other threads associated with the operand if there are other threads associated with the operand.
6. The system of claim 3, wherein the transaction scheduling manager releases a lock on the operand without other threads associated with the operand, allocating transaction management resources to a second heterogeneous data source node.
7. The system of claim 5, wherein the transaction scheduling manager is further configured to send a transaction management end message to the first local transaction manager after terminating the other threads associated with the operands.
8. The system of claim 6, wherein the second heterogeneous data source node is configured to process other second transaction processing requests using the transaction management resource and store the processing result to the thread variable corresponding to the second heterogeneous data source node.
9. The system of claim 7, wherein the first heterogeneous data source node is further configured to execute the first transaction request and store the execution result to a thread variable corresponding to the first heterogeneous data source node.
10. The system according to claim 8 or 9, wherein the global transaction manager further includes a transaction recovery manager, and the transaction recovery manager is further configured to determine whether the heterogeneous data source node performs an error according to any one thread variable, control all the heterogeneous data source nodes to perform rollback when any one of the heterogeneous data source nodes performs the error, and control all the heterogeneous data source nodes to submit an execution result to the global transaction manager when none of the heterogeneous data source nodes performs the error.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011628305.9A CN112685142A (en) | 2020-12-30 | 2020-12-30 | Distributed data processing system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011628305.9A CN112685142A (en) | 2020-12-30 | 2020-12-30 | Distributed data processing system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112685142A true CN112685142A (en) | 2021-04-20 |
Family
ID=75455877
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011628305.9A Pending CN112685142A (en) | 2020-12-30 | 2020-12-30 | Distributed data processing system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112685142A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023082992A1 (en) * | 2021-11-12 | 2023-05-19 | 阿里巴巴（中国）有限公司 | Data processing method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101094173A (en) * | 2007-06-28 | 2007-12-26 | 上海交通大学 | Integrated system of data interchange under distributed isomerical environment |
| US20080027987A1 (en) * | 2006-07-31 | 2008-01-31 | Oracle International Corporation | Replicating data between heterogeneous data systems |
| US20100100690A1 (en) * | 2008-10-21 | 2010-04-22 | Microsoft Corporation | System to reduce interference in concurrent programs |
| CN103942234A (en) * | 2013-01-21 | 2014-07-23 | 中国电信股份有限公司 | Method for operating multiple heterogeneous databases, middleware device and system |
| CN110659327A (en) * | 2019-08-16 | 2020-01-07 | 平安科技（深圳）有限公司 | Method and related device for realizing interactive query of data between heterogeneous databases |
| CN111858056A (en) * | 2020-07-24 | 2020-10-30 | 南方电网数字电网研究院有限公司 | Task scheduling method and device, computer equipment and storage medium |
-
2020
- 2020-12-30 CN CN202011628305.9A patent/CN112685142A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080027987A1 (en) * | 2006-07-31 | 2008-01-31 | Oracle International Corporation | Replicating data between heterogeneous data systems |
| CN101094173A (en) * | 2007-06-28 | 2007-12-26 | 上海交通大学 | Integrated system of data interchange under distributed isomerical environment |
| US20100100690A1 (en) * | 2008-10-21 | 2010-04-22 | Microsoft Corporation | System to reduce interference in concurrent programs |
| CN103942234A (en) * | 2013-01-21 | 2014-07-23 | 中国电信股份有限公司 | Method for operating multiple heterogeneous databases, middleware device and system |
| CN110659327A (en) * | 2019-08-16 | 2020-01-07 | 平安科技（深圳）有限公司 | Method and related device for realizing interactive query of data between heterogeneous databases |
| CN111858056A (en) * | 2020-07-24 | 2020-10-30 | 南方电网数字电网研究院有限公司 | Task scheduling method and device, computer equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023082992A1 (en) * | 2021-11-12 | 2023-05-19 | 阿里巴巴（中国）有限公司 | Data processing method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104793988B (en) | The implementation method and device of integration across database distributed transaction | |
| US5923833A (en) | Restart and recovery of OMG-compliant transaction systems | |
| US7349970B2 (en) | Workload management of stateful program entities | |
| EP2754284B1 (en) | Idempotence for database transactions | |
| US7844720B2 (en) | Managing database connections | |
| US8209699B2 (en) | System and method for subunit operations in a database | |
| EP2600246B1 (en) | Batch processing of business objects | |
| JP6069339B2 (en) | Oracle Rewind: Metadata Driven Undo | |
| EP0649089A1 (en) | System and method for optimizing message flows between agents in distributed computations | |
| US7328213B2 (en) | Transaction processing method, transaction control apparatus and program thereof | |
| EP3238421B1 (en) | System for high-throughput handling of transactions in data-partitioned, distributed, relational database management system | |
| US20130117226A1 (en) | Method and A System for Synchronizing Data | |
| JPH1165863A (en) | Common resource managing method | |
| KR20140147812A (en) | Systems and methods for supporting inline delegation of middle-tier transaction logs to database | |
| CN108845866B (en) | Method and apparatus for processing distributed transactions | |
| US7712096B2 (en) | Method, system, and storage medium for dynamically reordering resource participation in two-phase commit to heuristically optimize for last-agent optimization | |
| CN112039970B (en) | Distributed business lock service method, server, system and storage medium | |
| US10698767B1 (en) | Decentralized management of multi-service workflows | |
| CN113268471B (en) | Method, proxy connection pool, system, device and medium for processing distributed transaction | |
| WO2008101756A1 (en) | Method and system for concurrent message processing | |
| US7752225B2 (en) | Replication and mapping mechanism for recreating memory durations | |
| CN112685142A (en) | Distributed data processing system | |
| CN108446167B (en) | Distributed transaction processing method and system | |
| CN111400097A (en) | Data backup method, device, system and computer readable storage medium | |
| CN109901933B (en) | Operation method and device of business system, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |