Conflict avoidance in data store replication
View Patent ↗A conflict avoidance system is provided. The conflict avoidance system comprises a first data store provided at a first geographic location and a second data store at a second geographic location, where the first and second data stores are replications of one another. The conflict avoidance system also comprises a conflict avoidance module operable to receive a data store request from applications, wherein the conflict avoidance module communicates update data store requests to the first data store and communicates create data store requests and delete data store requests to the second data store.
1. A conflict avoidance system, comprising,
a first data store;
a second data store, the first and second data stores defined as replications of one another;
a conflict avoidance module operable to receive a data store request from a plurality of applications;
a rule used by the conflict avoidance module, the conflict avoidance module operable based on a default of the rule to communicate an update data store requests from one of the applications to the first data store and further based on the default of the rule to communicate a create data store request and a delete data store request from one of the applications to the second data store.
2. The system of claim 1 , wherein the rule further includes a work unit rule used by the conflict avoidance module in response to receiving a data store request to define a unit of work associated with the data store request, to associate the unit of work with one of the data stores based on the data store request, and to route subsequent data store requests associated with the unit of work to the associated data store, the unit of work including an identifier.
3. The system of claim 2 , wherein the identifier is provided by one of the applications to associate related data store requests.
4. The system of claim 2 , wherein the conflict avoidance module is further operable to destroy the unit of work after a time period has expired during which no data requests are received associated with the unit of work.
5. The system of claim 2 , wherein the conflict avoidance module associates data store requests with the unit of work based at least in part on an identify of one of the applications.
6. The system of claim 2 , wherein the conflict avoidance module associates data store requests with the unit of work based at least in part on a primary key of a data store entry.
7. The system of claim 2 , wherein conflict avoidance module associates data store requests with the unit of work based at least in part on an identity of a user employing one of the applications.
8. The system of claim 1 , wherein the data store requests are further defined as insert, read, update, delete.
9. The system of claim 1 , wherein the rule further includes a load balancing rule used by the conflict avoidance module to distribute read requests to the first and second data stores according to a load balancing mechanism.
10. The system of claim 1 , further comprising a replication component operable to replicate data between one or more data stores.
11. The system of claim 1 , wherein the a first data store is provided at a first geographic location and the second data store is provided at a second geographic location.
12. A method of avoiding conflicts in replicated data stores, the method comprising:
determining a type of request received from a plurality of applications;
communicating update type data requests from the plurality of applications to the first data store; and
communicating delete and insert type data requests from the plurality of applications to a second data store.
13. The method of claim 12 , further comprising:
occasionally replicating data from the first data store to the second data store; and
occasionally replicating data from the second data store to the first data store.
14. The method of claim 12 , further comprising:
defining a unit of work associated with a first data request, the unit of work identifying one of the data stores; and
communicating subsequent requests associated with the unit of work to the data store identified by the unit of work until the unit of work expires or is destroyed.
15. The method of claim 14 , wherein the unit of work is associated with the second data request based on at least one of an identify of the application, an identity of a user of the application, and a primary key of a data store entry.
16. The method of claim 14 , further comprising:
destroying the unit of work after the utility of the unit of work is lost.
17. The method of claim 14 , further comprising:
destroying the unit of work after a plurality of data requests are committed.