SYSTEMS AND METHODS FOR ASYNCHRONOUS DISTRIBUTED DATABASE MANAGEMENT

• US 20130036089A1
• Filed: 08/01/2012
• Published: 02/07/2013
• Est. Priority Date: 08/01/2011
• Status: Abandoned Application

• Current Assignee: Ifwe Inc.
• Original Assignee: Tagged Incorporated
• Inventors: Lucas, Jason
• Application Number:
  US13/564,242
• Publication Number:
  US 20130036089A1
• Time in Patent Office: Days
• US Class Current: 707/615
• CPC Class Codes: G06F 16/2315 Optimistic concurrency control
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

Embodiments of the present disclosure include systems and methods for asynchronous distributed database management. In one embodiment, the systems and methods wait to execute or update a database transaction or command until specific conditions are satisfied, essentially divorcing the read-time from update-time in evaluation of a single expression. Accordingly, the systems and methods described herein can, in some instances, resolve the temporary inconsistencies without aborting and/or otherwise terminating a database transaction that would otherwise be aborted.

Claims

1. A method of asynchronous distributed database management, the method comprising:

receiving, at a database management system, a database transaction associated with a transaction sequence from a client in a distributed database system, wherein the database transaction includes one or more assertions;

polling, at the database management system, a plurality of database resources regarding the validity of the one or more assertions included within the database transaction to achieve a consensus; and

updating, at the database management system, the database transaction in the distributed database system upon achieving the consensus if the consensus is achieved within a timeout interval, wherein the consensus is not initially achieved among the plurality of database resources.

2. The method of claim 1, further comprising:

notifying, at the database management system, the client in the distributed database that the database transaction has been aborted if the consensus is not achieved within the timeout interval.

3. The method of claim 1, wherein the database transaction is initiated by an application running on the client.

4. The method of claim 1, further comprising:

prior to updating the distributed database system, notifying the client that the database transaction has completed successfully.

5. The method of claim 1, wherein the timeout interval comprises a duration of time between one half of a second and three seconds.

6. The method of claim 1, wherein the timeout interval comprises a duration of time less than one half of a second.

7. The method of claim 1, wherein updating the distributed database system further comprises:

asynchronously reconciling the database transaction with one or more other database transactions in the distributed database system.

8. The method of claim 1, further comprising:

prior to updating the distributed database system, reading information related to the database transaction from the distributed database system; and

transferring the information to the client regardless of whether the consensus has been achieved.

9. The method of claim 1, further comprising:

receiving, at the database management system, a second database transaction associated with a second transaction sequence from a second client in the distributed database system, wherein the second database transaction includes one or more second assertions, and wherein the one or more second assertions require reading the information related to the database transaction.

10. The method of claim 1, wherein updating the distributed database system further comprises:

committing the database transaction to a global transaction sequence; and

replicating the global transaction sequence across the plurality of database resources of the distributed database.

11. The method of claim 1, further comprising:

determining, at the database management system, a likelihood that the consensus can be achieved.

12. The method of claim 11, further comprising:

setting, at the database management system, the timeout interval based upon the likelihood that the consensus can be achieved.

13. The method of claim 1, wherein the plurality of database resources comprise one or more of other database management systems in the distributed database system or one or more storage management systems in the distributed database system.

14. A method of asynchronous distributed database management, the method comprising:

receiving, at a database management system, a database transaction associated with a transaction sequence from a client in a distributed database system, wherein the database transaction includes one or more assertions;

processing, at the database management system, the database transaction to identify the one or more assertions, wherein the one or more assertions must have a specific configuration in order to update the database transaction in the distributed database system;

determining, at the database management system, a first configuration among a plurality of database resources regarding the one or more assertions at a first time, wherein the first configuration is different than the specific configuration; and

updating, at the database management system, the database transaction in the distributed database system at a second time if a second configuration among the plurality of database resources regarding the one or more assertions is the same as the specific configuration at the second time.

15. The method of claim 14, wherein the specific configuration requires that the one or more assertions be valid.

16. The method of claim 14, further comprising:

notifying, at the database management system, the client in the distributed database that the database transaction has been aborted if the second configuration is different than the specific configuration at the second time.

17. The method of claim 14, wherein the database transaction is initiated by an application running on the client.

18. The method of claim 17, further comprising:

prior to updating the distributed database system, notifying the application that the database transaction has completed successfully.

19. The method of claim 14, wherein updating the distributed database system further comprises:

asynchronously reconciling the database transaction with one or more other database transactions in the distributed database system.

20. The method of claim 14, further comprising:

prior to updating the distributed database system, reading information related to the database transaction from the distributed database system; and

transferring the information to the client regardless of whether the consensus has been achieved.

21. The method of claim 14, further comprising:

receiving, at the database management system, a second database transaction associated with a second transaction sequence from a second client in the distributed database system, wherein the second database transaction includes one or more second assertions, and wherein the one or more second assertions require reading the information related to the database transaction.

22. The method of claim 14, wherein updating the distributed database system further comprises:

committing the database transaction to a global transaction sequence; and

replicating the global transaction sequence across the plurality of database resources of the distributed database.

23. The method of claim 14, further comprising:

determining, at the database management system, a likelihood that the consensus can be achieved.

24. The method of claim 23, further comprising:

setting, at the database management system, the timeout interval based upon the likelihood that the consensus can be achieved.

25. The method of claim 14, wherein the resources comprise one or more of other database management systems in the distributed database system or storage management systems in the distributed database system.

26. A database management system comprising:

a processing unit;

an interface configured to receive a database transaction associated with a transaction sequence from a client in a distributed database system, wherein the database transaction includes one or more assertions;

a memory unit having instructions stored thereon, wherein the instructions, when executed by the processing unit, cause the processing unit to process the database transaction to identify the one or more assertions, wherein the one or more assertions must have a specific configuration in order to update the database transaction in the distributed database system, determine a first configuration among a plurality of database resources regarding the one or more assertions at a first time, wherein the first configuration is different than the specific configuration, and update the database transaction in the global transaction sequence at a second time if a second configuration among the plurality of database resources regarding the one or more assertions is the same as the specific configuration at the second time.

27. The database management system of claim 26, wherein the specific configuration requires that the one or more assertions be valid.

28. The database management system of claim 26, wherein the instructions, when executed by the processing unit, further cause the processing unit to notify the client in the distributed database system that the database transaction has been aborted if the second configuration is different than the specific configuration at the second time.

29. The database management system of claim 26, wherein the database transaction is initiated by an application running on the client.

30. The database management system of claim 29, wherein the instructions, when executed by the processing unit, further cause the processing unit to notify the application that the database transaction has completed successfully prior to updating the distributed database system.

31. The database management system of claim 26, wherein the instructions, when executed by the processing unit, further cause the processing unit to determine a likelihood that the consensus can be achieved.

32. The database management system of claim 31, wherein the instructions, when executed by the processing unit, further cause the processing unit to set a timeout interval, wherein the second time is less than or equal to the timeout interval.

33. A database management system comprising:

a processing unit;

an interface configured to receive a database transaction associated with a transaction sequence from a client in a distributed database system, wherein the database transaction includes one or more assertions;

a memory unit having instructions stored thereon, wherein the instructions, when executed by the processing unit, cause the processing unit to repeatedly query database resources regarding the validity of one or more assertions included within the database transaction to achieve a consensus, and update the database transaction in the distributed database system upon achieving the consensus if the consensus is achieved within a timeout interval, wherein the consensus is not initially achieved among the plurality of resources, and notify the client in the distributed database that the database transaction has been aborted if the consensus is not achieved within the timeout interval.

34. A database management system comprising:

means for receiving a database transaction associated with a transaction sequence from a client in a distributed database system, wherein the database transaction includes one or more assertions;

means for polling a plurality of database resources regarding the validity of the one or more assertions included within the database transaction to achieve a consensus; and

means for updating the database transaction in the distributed database system upon achieving the consensus if the consensus is achieved within a timeout interval, wherein the consensus is not initially achieved among the plurality of database resources.