METHODS AND APPARATUS FOR A DISTRIBUTED DATABASE WITHIN A NETWORK

• US 20170132257A1
• Filed: 07/08/2016
• Published: 05/11/2017
• Est. Priority Date: 08/28/2015
• Status: Active Grant

• Current Assignee: Hedera Hashgraph LLC
• Original Assignee: Swirlds, Inc.
• Inventors: BAIRD, III, Leemon C.
• Granted Patent: US 10,318,505 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/2255 Hash tables
• 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 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

In some embodiments, an instance of a distributed database can be configured at a first compute device within a set of compute devices that implements the distributed database via a network. A database convergence module can define a first event linked to a first set of events and receive, from a second compute device from the set of compute devices, a second event (1) defined by the second compute device and (2) linked to a second set of events. The database convergence module can define a third event linked to the first event and the second event. The database convergence module can identify an order associated with a third set of events based at least on the first set of events and the second set of events, and store in the instance of the distributed database the order associated with the third set of events.

Claims

1-20. -20. (canceled)

21. A method, comprising:

receiving, at a first compute device from a plurality of compute devices, data associated with a first transaction, each compute device from the plurality of compute devices having a separate instance of a distributed database;

receiving, from a second compute device from the plurality of compute devices, data associated with a second transaction;

calculating a transaction order based on the first transaction and the second transaction;

defining a first state value based on the first transaction, the second transaction, the transaction order and a second state value stored as associated with a first version of a fast clone database implemented in a physical database;

defining a second version of the fast clone database based on the first state value such that a link is defined between the first version and the second version and a link is defined between the first version and a third version of the fast clone database including the second state value but not the first state value; and

storing the first state value in the physical database and as associated with the second version of the first clone database.

22. The method of claim 21, further comprising:

retrieving the first state value in response to a query to the second version of the fast clone database; and

retrieving the second state value in response to a query to the third version of the fast clone database.

23. The method of claim 21, wherein the first state value and the second state value are associated with a state of the first compute device, the method further comprising:

receiving an instruction to delete a state value associated with the second compute device from the third version of the fast clone database;

disassociating the state value associated with the second compute device from (1) the third version of the fast clone database and (2) the first version of the fast clone database; and

associating the state value associated with the second compute device with the second version of the fast clone database.

24. The method of claim 21, wherein the first state value and the second state value are associated with a state of the first compute device, the state of the first compute device being associated with at least one of an amount of crypto currency held by the first compute device, an indication of ownership of an item, or a state of a multi-player game.