Multi-Path Replication in Databases
Abstract
Systems, methods and computer program products for multi-path replication in databases are described herein. A non-limiting embodiment includes instantiating a plurality of replicate connections to a replicate database, providing transactions to the replicate database through a plurality of transaction streams, where the transaction streams associated with respective instantiated replicate connections. Transactions occurring in distinct transaction streams are applied, in parallel, at the replicate database. Another non-limiting embodiment includes instantiating a plurality of replication sender threads, where the replication sender threads communicate in parallel with respective replication servers over respective replication paths. Data sharing one or more attributes can be bound to a replication path in communication with the respective replication servers.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A computer-implemented method for database replication, comprising:
instantiating a plurality of replication sender threads, said replication sender threads communicating in parallel with respective replication servers over respective replication paths; and binding data sharing one or more attributes to a replication path in communication with said respective replication servers.
2 . The method of claim 1 , further comprising:
binding a database object to a channel for replication; and providing said bound object over said channel to a replication server dedicated to said channel.
3 . The method of claim 1 , further comprising:
replicating data sharing a first set of attributes over a first replication path; and replicating data sharing a second set of attributes over a second replication path, wherein said first set of attributes is distinct from said second set of attributes, and wherein said first path and said second path are associated with respective replication servers.
4 . The method of claim 1 , wherein said attributes include one or more of an object type, a table name, an identifier and a statement category.
5 . The method of claim 1 , further comprising:
defining a plurality of destinations at a source database; and delivering replicate data, in parallel, to said destinations.
6 . The method of claim 1 , further comprising:
grouping data with shared attributes according to the shared attributes to create a group.
7 . The method of claim 6 , wherein binding data sharing one or more attributes to the replication path comprises binding the group to the replication path.
8 . The method of claim 1 , further comprising:
identifying a replication path having less transaction congestion than at least one other replication path.
9 . The method of claim 8 , wherein binding data sharing one or more attributes to a replication comprises binding the data sharing one or more attributes to the identified replication path.
10 . The method of claim 1 , wherein binding data sharing one or more attributes to a replication path comprises binding the data according to a replication priority associated with the data.
11 . A system for database replication, comprising:
a memory configured to store data; and one or more processors communicatively coupled to the memory, wherein the processors are configured execute computer instructions stored on the memory, wherein the computer instructions cause the one or more processors to perform steps comprising:
instantiating a plurality of replication sender threads, said replication sender threads communicating in parallel with respective replication servers over respective replication paths; and
binding data sharing one or more attributes to a replication path in communication with said respective replication servers.
12 . The system of claim 1 , wherein the computer instructions cause the one or more processors to perform steps further comprising:
binding a database object to a channel for replication; and providing said bound object over said channel to a replication server dedicated to said channel.
13 . The system of claim 11 , wherein the computer instructions cause the one or more processors to perform steps further comprising:
replicating data sharing a first set of attributes over a first replication path; and replicating data sharing a second set of attributes over a second replication path, wherein said first set of attributes is distinct from said second set of attributes, and wherein said first path and said second path are associated with respective replication servers.
14 . The system of claim 11 , wherein the attributes include one or more of an object type, a table name, an identifier and a statement category.
15 . The system of claim 11 , wherein the computer instructions cause the one or more processors to perform steps further comprising:
defining a plurality of destinations at a source database; and delivering replicate data, in parallel, to said destinations.
16 . The system of claim 11 , wherein the computer instructions cause the one or more processors to perform steps further comprising:
grouping data with shared attributes according to the shared attributes to create a group.
17 . The system of claim 16 , wherein binding data sharing one or more attributes to the replication path comprises binding the group to the replication path.
18 . The system of claim 11 , wherein the computer instructions cause the one or more processors to perform steps further comprising:
identifying a replication path having less transaction congestion than at least one other replication path.
19 . The system of claim 18 , wherein binding data sharing one or more attributes to a replication comprises binding the data sharing one or more attributes to the identified replication path.
20 . The system of claim 11 , wherein binding data sharing one or more attributes to a replication path comprises binding the data according to a replication priority associated with the data.Join the waitlist — get patent alerts
Track US2015046400A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.