Persistent data storage techniques

• US 9,830,348 B2
• Filed: 12/05/2014
• Issued: 11/28/2017
• Est. Priority Date: 10/13/2000
• Status: Expired due to Fees

• Current Assignee: MIOsoft Corporation
• Original Assignee: MIOsoft Corporation
• Inventors: Barabas, Albert B., Siepmann, Ernst M., van Gulik, Mark D. A.
• Primary Examiner(s): To, Baoquoc N
• Application Number:
  US14/561,281
• Publication Number:
  US 20150088820A1
• Time in Patent Office: 1,089 Days
• Field of Search: 707648, 707690, 70799901, 709 26, 709201, 705 713, 325379
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database

Abstract

A database is maintained that stores data persistently. Tasks are accepted from task sources. At least some of the tasks have competing requirements for use of regions of the database. Each of the regions includes data that is all either locked or not locked for writing at a given time. Each of the regions is associated with an available processor. For each of the tasks, jobs are defined each of which requires write access to regions that are to be accessed by no more than one of the processors. Jobs are distributed for concurrent execution by the associated processors.

Claims

1. A computer-implemented method comprising

accepting from a source a task or a job to be executed in a persistently stored database, the task or job corresponding to a transaction to be committed, the task or job requiring access to change specific data in the database in order to execute the task or job, the data in the database being consistent and being subject to another conflicting task or job,

before the task or job has been executed, providing an acknowledgement to the source indicating that the task or job is guaranteed to be executed,

the task or job to be executed in the database notwithstanding the conflicting task or job and the task or job to be executed in a manner to maintain the consistency of the data pieces in the database.

2. The method of claim 1 comprising sending to the source an acknowledgement that the task or job has been completed.

3. The method of claim 1 in which the task or job is assigned to a contention space.

4. The method of claim 1 in which the database comprises an object-oriented database.

5. The method of claim 1 in which the database is distributed among storage devices at different locations interconnected by a network.

6. The method of claim 1 in which maintaining the consistency comprises maintaining a relationship that enables a process to reach the specific data from other data in the database or vice versa.

7. The method of claim 1 in which maintaining the consistency comprises maintaining information about temporarily incomplete states of the specific data and the other data.

8. The method of claim 7 in which the information about temporarily incomplete states is communicated to processes that are to update at least one of the specific data and the other data.

9. The method of claim 1 in which maintaining the consistency comprises concurrent processing with respect to the specific data and other data.

10. The method of claim 1 in which the task or job comprises a transaction to be committed in the persistently stored database.

11. The method of claim 10 in which the transaction is associated with a commercial transaction.

12. The method of claim 1 in which the task or job comprises a transaction including jobs to be executed in the database.

13. The method of claim 1 in which the task comprises or is the basis of a job that updates data at a location in the database to be the same as other data.

14. The method of claim 1 in which the task or job relates to one or more records to be loaded in the database.

15. The method of claim 1 comprising processing jobs associated with the task in a stream processor.

16. The method of claim 1 comprising accepting from the source additional tasks each requiring updating of data, and executing each of the tasks individually by executing associated jobs, the execution of the jobs being coordinated by a stream processor.

17. The method of claim 1 in which, while the task or job is being executed in the persistently stored database and the consistency of data is being maintained, executing a task that requires access to read data in the database.

18. The method of claim 1 in which data of the database is stored in memory.

19. The method of claim 18 in which the data stored in memory comprises an index that includes the data.

20. The method of claim 1 in which the data for which the consistency is maintained comprise data in two different storage devices at two different locations, data in two different non-conflicting regions, data in the database and data in an index, or data in two different physical clusters.

21. The method of claim 1 comprising

accepting additional tasks or jobs having competing requirements for use of regions of the database,

associating each of the regions with an available processor,

defining, for each of the tasks or jobs, jobs each of which requires write access to regions that are to be accessed by no more than one of the processors, and

distributing the jobs for concurrent execution by the associated processors.

22. The method of claim 1 in which the task comprises matching of a new item of data to be added to the database with data stored in the database or other data, the task spawns matching jobs for matching the data item to the data stored in the database or to other data, the matching jobs provide replies, the replies are collapsed into a list of matching data, the matching data of the list are merged, and update jobs are spawned to update the matching data.

23. The method of claim 22 in which the new item of data is associated with a real world object or person.

24. The method of claim 1 in which consistency is maintained between data on different storage devices at different locations of the network or between data in the database and data in an index.

25. The method of claim 1 comprising completing the task or job and maintaining consistency of the data pieces after a failure of a processor that is participating in the execution of the task or job.

26. The method of claim 1 in which the task comprises or is the basis of a job that is not to update data in the database.

27. The method of claim 1 in which the source comprises an application.