Balancing latency and consistency requirements during data replication
First Claim
1. A method for balancing latency and consistency requirements during data replication, the method comprising:
- defining, by one or more processors, a set of strategies representative of different types of inconsistencies between a first database and a second database, wherein the different types of inconsistencies vary with respect to details of a particular replication technology;
specifying, by one or more processors, a latency threshold at which a first type of inconsistency is allowed, based on a user input of a cost related to the latency threshold, wherein the type of inconsistency is selected from the set of strategies;
determining, by one or more processors, that a requested replication exceeds the latency threshold; and
moving, by one or more processors, data into a target database, wherein latency is dynamically balanced with data consistency, based on testing an algorithm from a set of algorithms, recording statistics that the algorithm provides about a rate of replication, determining the algorithm provides a best rate of replication, and using the algorithm to move the data into the target database, wherein the algorithm is retested if latency remains above the latency threshold.
2 Assignments
0 Petitions
Accused Products
Abstract
In an approach for balancing latency and consistency requirements during data replication, a processor defines a set of strategies representative of different types of inconsistencies between a first database and a second database, wherein the different types of inconsistencies vary with respect to details of a particular replication technology. A processor specifies a latency threshold at which a first type of inconsistency is allowed, based on user input of business information to enhance business value, wherein the type of inconsistency is selected from the set of strategies. A processor determines that a requested replication crosses the latency threshold. A processor pushes data into a target database, wherein latency is dynamically balanced with data consistency, based on the latency threshold.
17 Citations
20 Claims
-
1. A method for balancing latency and consistency requirements during data replication, the method comprising:
-
defining, by one or more processors, a set of strategies representative of different types of inconsistencies between a first database and a second database, wherein the different types of inconsistencies vary with respect to details of a particular replication technology; specifying, by one or more processors, a latency threshold at which a first type of inconsistency is allowed, based on a user input of a cost related to the latency threshold, wherein the type of inconsistency is selected from the set of strategies; determining, by one or more processors, that a requested replication exceeds the latency threshold; and moving, by one or more processors, data into a target database, wherein latency is dynamically balanced with data consistency, based on testing an algorithm from a set of algorithms, recording statistics that the algorithm provides about a rate of replication, determining the algorithm provides a best rate of replication, and using the algorithm to move the data into the target database, wherein the algorithm is retested if latency remains above the latency threshold. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A computer program product for balancing latency and consistency requirements during data replication, the computer program product comprising:
-
one or more computer readable storage media and program instructions stored on the one or more computer readable storage media, the program instructions comprising; program instructions to define a set of strategies representative of different types of inconsistencies between a first database and a second database, wherein the different types of inconsistencies vary with respect to details of a particular replication technology; program instructions to specify a latency threshold at which a first type of inconsistency is allowed, based on a user input of a cost related to the latency threshold, wherein the type of inconsistency is selected from the set of strategies; program instructions to determine that a requested replication exceeds the latency threshold; and program instructions to push data into a target database, wherein latency is dynamically balanced with data consistency, based on testing an algorithm from a set of algorithms, recording statistics that the algorithm provides about a rate of replication, determining the algorithm provides a best rate of replication, and using the algorithm to move the data into the target database, wherein the algorithm is retested if latency remains above the latency threshold. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A computer system for balancing latency and consistency requirements during data replication, the computer system comprising:
-
one or more computer processors, one or more computer readable storage media, and program instructions stored on the computer readable storage media for execution by at least one of the one or more processors, the program instructions comprising; program instructions to define a set of strategies representative of different types of inconsistencies between a first database and a second database, wherein the different types of inconsistencies vary with respect to details of a particular replication technology; program instructions to specify a latency threshold at which a first type of inconsistency is allowed, based on a user input of a cost related to the latency threshold, wherein the type of inconsistency is selected from the set of strategies; program instructions to determine that a requested replication exceeds the latency threshold; and program instructions to push data into a target database, wherein latency is dynamically balanced with data consistency, based on testing an algorithm from a set of algorithms, recording statistics that the algorithm provides about a rate of replication, determining the algorithm provides a best rate of replication, and using the algorithm to move the data into the target database, wherein the algorithm is retested if latency remains above the latency threshold. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification