Database with data integrity maintenance

1. A method for maintaining database integrity, the method comprising:

receiving, by one or more processors coupled to non-transitory memory, event data from a producer, the event data having a format different from a predefined schema;

converting, by the one or more processors, the received event data to a standard set of ledger entries according to the predefined schema, the standard set of ledger entries comprising a first edge object identifying a first relationship between a first account and a second account;

publishing, by the one or more processors, the converted entries to a database by grouping the first edge object with a second edge object identifying a second relationship between the first account and the second account; and

responsive to determining, by the one or more processors, based on a mismatch of a double-entry in ledger entries published to the database, that two accounts in the database do not balance out, performing, by the one or more processors, a remedial action to maintain the database integrity.

2. The method of claim 1 , further comprising transmitting, by the one or more processors, a data integrity violation alert to the producer upon determining that the two accounts do not balance out.

3. The method of claim 2 , further comprising:

receiving, by the one or more processors, a second event data from the producer in response to the data integrity violation alert; and

performing, by the one or more processors, the remedial action based on the received second event data.

4. The method of claim 1 , where the remedial action comprises adjusting, by the one or more processors, one of the two accounts to a zero balance if a value in the one account is less than a threshold value.

5. The method of claim 1 , wherein the event data includes a transfer of fungible commodities.

6. The method of claim 5 , wherein the fungible commodities include electricity or oil.

7. The method of claim 1 , wherein the publishing subtracts from one of the two accounts and adds to a second of the two accounts.

8. A system for maintaining database integrity, the system comprising:

one or more hardware processors; and

at least one memory storing instructions that, when executed by at least one processor among the processors, cause the system to perform operations comprising:

receiving event data from a producer, the event data having a format different from a predefined schema;

converting the received event data to a standard set of ledger entries according to the predefined schema, the standard set of ledger entries comprising a first edge object identifying a first relationship between a first account and a second account;

publishing the converted entries to a database by grouping the first edge object with a second edge object identifying a second relationship between the first account and the second account; and

responsive to determining, based on a mismatch of a double-entry in ledger entries published to the database, that two accounts in the database do not balance out, performing a remedial action to maintain the database integrity.

9. The system of claim 8 , wherein the operations further comprise transmitting a data integrity violation alert to the producer upon determining that the accounts do not balance out.

10. The system of claim 9 , wherein the operations further comprise:

receiving a second event data from the producer in response to the data integrity violation alert; and

performing the remedial action based on the received second event data.

11. The system of claim 8 , where the remedial action comprises adjusting one of the two accounts to a zero balance if a value in the one account is less than a threshold value.

12. The system of claim 8 , wherein the event data includes a transfer of fungible commodities.

13. The system of claim 12 , wherein the fungible commodities include electricity or oil.

14. The system of claim 8 , wherein the publishing subtracts from one of the two accounts and adds to a second of the two accounts.

15. A non-transitory machine-readable medium comprising instructions which, when read by a machine, cause the machine to perform operations for maintaining database integrity, the operations comprising, at least:

receiving event data from a producer, the event data having a format different from a predefined schema;

converting the received event data to a standard set of ledger entries according to the predefined schema, the standard set of ledger entries comprising a first edge object identifying a first relationship between a first account and a second account;

publishing the converted entries to a database by grouping the first edge object with a second edge object identifying a second relationship between the first account and the second account; and

responsive to determining, based on a mismatch of a double-entry in ledger entries published to the database, that two accounts in the database do not balance out, performing a remedial action to maintain the database integrity.

16. The medium of claim 15 , wherein the operations further comprise transmitting a data integrity violation alert to the producer upon determining that the accounts do not balance out.

17. The medium of claim 16 , wherein the operations further comprise:

receiving a second event data from the producer in response to the data integrity violation alert; and

performing the remedial action based on the received second event data.

18. The medium of claim 15 , where the remedial action comprises adjusting one of the two accounts to a zero balance if a value in the one account is less than a threshold value.

19. The medium of claim 15 , wherein the event data includes a transfer of fungible commodities.

20. The medium of claim 19 , wherein the fungible commodities include electricity or oil.

21. The medium of claim 15 , wherein the publishing subtracts from one of the two accounts and adds to a second of the two accounts.