Architecture of immutable database for bitemporal analysis

A computer-implemented method for processing a new transaction in a data processing system that includes a real-time interface, a processing engine, and a bitemporal ledger, the method comprising:

• generating a data stream associated with a data stream identifier, wherein the data stream identifier identifies a user account managed by the data processing system;
• receiving, in the data stream via the real-time interface, the new transaction and a retroactive transaction to be processed by the data processing system, wherein the real-time interface comprises a transaction stream for buffering a plurality of transactions and wherein the new transaction and the retroactive transaction are associated with the user account managed by the data processing system;
• identifying, in the bitemporal ledger in communication with the processing engine, a sequence of transactions associated with the new transaction and the retroactive transaction and an alternate sequence of transactions, wherein the sequence of transactions is implemented as a transaction timeline associated with the user account, and wherein the alternate sequence of transactions is implemented as an alternate timeline associated with the user account;
• appending, in the bitemporal ledger, the new transaction to the sequence of transactions according to temporal metadata associated with the new transaction, wherein the temporal metadata includes a first time indicating when the new transaction is created and a second time indicating when the new transaction is to take effect, wherein the bitemporal ledger is configured to prevent any transactions in the sequence of transactions from being overwritten during the appending, wherein the transaction timeline comprising the sequence of transactions and the new transaction reflects a current state of the user account, and wherein the sequence of transactions is time-ordered based at least in part on the second time of the temporal metadata;
• incorporating, in the bitemporal ledger, the retroactive transaction to the alternate sequence of transactions by replacing one transaction in the alternate sequence of transactions with the retroactive transaction;
• maintaining the alternate timeline separate from the transaction timeline in the bitemporal ledger, wherein the alternate sequence of transactions reflects an alternate state of the user account based on the retroactive transaction, and wherein the alternate sequence of transactions is time-ordered based at least in part on temporal metadata associated with the retroactive transaction;
• determining whether the alternate state of the user account includes an error;
• and
• merging, in the transaction timeline, in the bitemporal ledger, the current state of the user account with the alternate state of the user account based on the determining.

A non-transitory computer-readable medium storing instructions, the instructions, when executed by an immutable database that includes a processing engine, a real-time interface and a bitemporal ledger, cause the immutable database to perform operations comprising:

• generating a data stream associated with a data stream identifier, wherein the data stream identifier identifies a user account managed by the data processing system;
• receiving, in the data stream via the real-time interface, a new transaction and a retroactive transaction to be processed by the data processing system, wherein the real-time interface comprises a transaction stream for buffering a plurality of transactions and wherein the new transaction and the retroactive transaction are associated with the user account managed by the data processing system;
• identifying, in the bitemporal ledger in communication with the processing engine, a sequence of transactions associated with the new transaction and the retroactive transaction and an alternate sequence of transactions, wherein the sequence of transactions is implemented as a transaction timeline associated with the user account, and wherein the alternate sequence of transactions is implemented as an alternate timeline associated with the user account;
• appending, in the bitemporal ledger, the new transaction to the sequence of transactions according to temporal metadata associated with the new transaction, wherein the temporal metadata includes a first time indicating when the new transaction is created and a second time indicating when the new transaction is to take effect, wherein the bitemporal ledger is configured to prevent any transactions in the sequence of transactions from being overwritten, wherein the transaction timeline comprising the sequence of transactions and the new transaction reflects a current state of the user account, and wherein the sequence of transactions is time-ordered based at least in part on the second time of the temporal metadata;
• incorporating, in the bitemporal ledger, the retroactive transaction to the alternate sequence of transactions by replacing one transaction in the alternate sequence of transactions with the retroactive transaction;
• maintaining the alternate timeline separate from the transaction timeline in the bitemporal ledger, wherein the alternate sequence of transactions reflects an alternate state of the user account based on the retroactive transaction, and wherein the alternate sequence of transactions is time-ordered based at least in part on temporal metadata associated with the retroactive transaction;
• determining whether the alternate state of the user account includes an error;
• and
• merging, in the transaction timeline, in the bitemporal ledger, the current state of the user account with the alternate state of the user account based on the determining.