Peer to peer database

• US 8,571,882 B1
• Filed: 07/03/2007
• Issued: 10/29/2013
• Est. Priority Date: 07/05/2006
• Status: Expired due to Fees

• Current Assignee: Ronald J. Teitelbaum
• Original Assignee: Ronald J. Teitelbaum
• Inventors: Teitelbaum, Ronald J.
• Primary Examiner(s): O'Connor, Gerald J.
• Assistant Examiner(s): WINSTON III, EDWARD B
• Application Number:
  US11/824,817
• Time in Patent Office: 2,310 Days
• Field of Search: 717/164, 717/168, 709/201, 709/222, 709/223, 709/232, 705/2, 705/3
• US Class Current: 705/2
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 16/211 Schema design and management
• 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
• CPC Class Codes: G06F 2212/465 Structured object, e.g. database record
• CPC Class Codes: H04L 67/1076 Resource dissemination mechanisms or network resource keeping policies for optimal resource availability in the overlay network

Abstract

A system for providing database functionality on a peer-to-peer network is described that provides a highly scalable, fault tolerant, highly available, secure distributed transactions and reporting environment for application development and deployment.

Claims

1. A method of executing instructions stored on a non-transitory computer-readable storage medium, using at least one processor, to thereby execute relationship mapping for data of a peer-to-peer database, the peer-to-peer database including a plurality of data records which are uniquely identified for querying thereof within a namespace of the peer-to-peer network and which each are related to data objects which form a corresponding data record of the plurality of data records, comprising:

determining, using the at least one processor, a data object of the data objects to be persisted on the peer-to-peer database as part of a data record of the plurality of data records, the data object having a data network address;

associating, using the at least one processor, a redirection object with the data object, the redirection object including a network address and the data network address;

persisting, using the at least one processor, the redirection object on the peer to peer database; and

maintaining a connection between the data object at the data network address and the redirection object at the network address, wherein the redirection object provides a primary reference from the data object to its associated data record of the plurality of data records of the peer-to-peer database, and connections of the associated data record are independent of the connection between the data object and the redirection object.

5. The method of claim 1 wherein the redirection object is configured to maintain a link to current data stored on the peer-to-peer database.

6. The method of claim 1 wherein the redirection object is configured to maintain a history of data network addresses that hold previous peer-to-peer data objects previously linked using the redirection object.

7. The method of claim 1 wherein the redirection object is configured to provide a primary reference from an index to an associated data record in the peer-to-peer database, and wherein the peer-to-peer database is configured to update index values of the index independently of a manner in which the index and data records are linked.

8. The method of claim 1 wherein the redirection object is configured to manage local data caching.

9. The method of claim 1 wherein the redirection object is configured to manage composite data structures.

10. The method of claim 1 wherein the redirection object is configured to manage data of the peer-to-peer database including publishing, deleting or reorganizing the data on at least one peer-to-peer database node.

11. The method of claim 1 wherein the redirection object is configured to trigger a local process to publish, delete or reorganize data of the peer-to-peer database on at least one peer-to-peer database node.

12. The method of claim 1 wherein the redirection object is configured to manage data backup to a separate peer-to-peer database.

13. The method of claim 1 wherein the redirection object is configured to manage an association of composite data records.

14. The method of claim 1 wherein the redirection object is configured to trigger code to execute locally which writes data for a composite data record.

2. A method of executing instructions stored on a non-transitory computer-readable storage medium, using at least one processor, to thereby execute persisting data on a peer-to-peer database, the peer-to-peer database including a plurality of data records which are uniquely identified for querying thereof within a namespace of the peer-to-peer network and which each are related to data objects which form a corresponding data record of the plurality of data records, the method comprising:

determining, using the at least one processor, at least one data object associated with a data transaction, each data object being associated with a data network address on the peer-to-peer database;

determining, using the at least one processor, at least one storage node for each data object;

determining, using the at least one processor, a consistency of the at least one data object on a respective at least one storage node; and

determining, using the at least one processor, whether to write the at least one data object to the respective at least one storage node, based on the determining of the consistency.

15. The method of claim 2 wherein the storage node is a component of the peer-to-peer database that is locatable amongst other storage nodes of the peer-to-peer database as containing data being sought, based on characteristics of the data being sought.

16. The method of claim 2 wherein the peer-to-peer database nodes are configured to store relational data.

17. The method of claim 2 wherein the peer-to-peer database nodes are configured to store peer-to-peer data indexes.

18. The method of claim 2 wherein the peer-to-peer database nodes are configured to store peer-to-peer redirection objects, each redirection object associated with a corresponding data object and including a network address and the data network address of the corresponding data object, wherein a connection is maintained between the data object at the data network address and the redirection object at the network address, wherein the redirection object provides a primary reference from the data object to its associated data record of the plurality of data records of the peer-to-peer database, and connections of the associated data record are independent of the connection between the data object and the redirection object.

19. The method of claim 2 wherein the peer-to-peer database nodes are configured to store programming code.

20. The method of claim 2 wherein the peer-to-peer database nodes are configured to store database triggers that maintain data consistency.

21. The method of claim 2 wherein the peer-to-peer database nodes configured to store security information for related data security techniques.

22. The method of claim 2 wherein the peer-to-peer database nodes are configured to store database schema information

23. The method of claim 2 wherein the peer-to-peer database nodes are configured to store composite data.

24. The method of claim 2 wherein the peer-to-peer database nodes are configured to execute methods deferred or forked from other processes.

3. A method of executing instructions stored on a non-transitory computer-readable storage medium, using at least one processor, to thereby execute persisting composite elements on a peer-to-peer database, the peer-to-peer database including a plurality of data records which are uniquely identified for querying thereof within a namespace of the peer-to-peer network and which each are related to data objects which form a corresponding data record of the plurality of data records, the method comprising:

determining, using the at least one processor, a composite definition for at least one class on the peer-to-peer database;

determining, using the at least one processor, a data transaction including data objects of the composite definition;

assigning, using the at least one processor, a composite network address to the data objects; and

storing, using the at least one processor, the data objects at the composite network address on the peer-to-peer database.

25. The method of claim 3 wherein data linked into the composite definition is addressable and stored on the peer-to-peer database at individual data element network locations, and wherein the peer-to-peer database is configured to read the linked data together when referenced from the composite definition storage location.

26. The method of claim 3 wherein a process that updates a single composite data object triggers updates to related, stored composite records on the peer-to-peer database.

27. The method of claim 3 wherein composite definition updates are deferred or forked to another process on a peer-to-peer database node.

4. A method of executing instructions stored on a non-transitory computer-readable storage medium, using at least one processor, to thereby execute persisting data using segregated address spaces on a peer-to-peer database, the peer-to-peer database including a plurality of data records which are uniquely identified for querying thereof within a namespace of the peer-to-peer network and which each are related to data objects which form a corresponding data record of the plurality of data records, the method comprising:

accessing, using the at least one processor, the data objects at a node of the peer-to-peer database;

subscribing, using the at least one processor, a local area network (LAN) of the node to the data objects;

committing, using the at least one processor, updates to the data objects on the LAN as a segregated address space of the namespace of the peer-to-peer network; and

committing, using the at least one processor, the updates to the corresponding data records of the peer-to-peer database.

28. The method of claim 4 wherein the updates to the data objects that are committed on the LAN include data of local data consumers on the LAN.

29. The method of claim 4 wherein the updates to the data objects that are committed on the LAN include data that is used as a persistent backup for defined peer-to-peer data.

30. The method of claim 4 wherein the updates to the data objects that are committed on the LAN include data of a process that requires data retrieval for the peer-to-peer database.

31. The method of claim 4 wherein the updates to the data objects that are committed on the LAN include data stored using different security requirements.

32. The method of claim 4 wherein the updates to the data objects that are committed on the LAN include private data that is not available on the peer-to-peer database outside of the LAN.

33. The method of claim 4 wherein the updates to the data objects that are committed on the LAN include data maintained in private by a creator thereof.