Reconciliation of data stored on permissioned database storage across independent computing nodes

A system comprising:

• a resource manager in communication with a network;
• an execution platform comprising a plurality of processing nodes, wherein each of the plurality of processing nodes is dedicated to only one client account of a plurality of client accounts coupled to the resource manager;
• a database comprising a shared permissioned ledger, wherein the shared permissioned ledger is stored across a plurality of independent ledger instances, wherein each of the plurality of independent ledger instances is dedicated to one client account of the plurality of client accounts such that a first ledger instance dedicated to a first client account is stored on independent storage resources from a second ledger instance dedicated to a second client account;
• a data ingestion engine comprising a plurality of node-specific ingestors, wherein each of the plurality of node-specific ingestors is dedicated to a single client account associated with the database, and wherein each of the plurality of node-specific ingestors is assigned to one data stream event channel pushed by one of the plurality of client accounts, and wherein the data ingestion engine independently scales processing and storage resources for each of the plurality of node-specific ingestors;
• wherein the resource manager comprises one or more processors for executing instructions stored in non-transitory computer readable storage media, the instructions comprising:
• reducing latency in data analysis with a stateless Application Program Interface that automatically scales and load-balances processing resources on the execution platform independently from scaling storage resources on the shared permissioned ledger based on need, wherein the shared permissioned ledger comprises scalable storage hardware partitioned to the plurality of independent ledger instances based on need;
• defining a settlement group comprising one or more settlement clients from the plurality of client accounts, wherein the settlement group comprises trading rules that apply to each of the one or more settlement clients;
• identifying ingested data associated with each of the one or more settlement clients, wherein the ingested data is ingested by one or more node-specific ingestors of the data ingestion engine;
• normalizing the ingested data to a canonical format readable by the resource manager to generate normalized data;
• partitioning the normalized data across the plurality of ledger instances of the shared permissioned ledger based on ownership, wherein the first client account assigned to the first ledger instance can only read or write to data stored on the first ledger instance;
• assigning the ingested data an encryption level on a key hierarchy within the shared permissioned ledger based on content of the ingested data;
• encrypting at least a portion of the ingested data with a client-specific key associated with the encryption level;
• tracking real-time liquidity, obligations, and exposures between each of the one or more settlement clients of the settlement group based on data stored on the shared permissioned ledger;
• and
• authenticating an observer node associated with at least one of the one or more settlement clients, wherein the observer node is granted read access to certain data on the shared permissioned ledger;
• wherein the database is not distributed across a blockchain network;
• and
• wherein the shared permissioned ledger comprises permissions such that the first client account does not have permission to access data stored on the second ledger for the second client account.