Computing system providing blockchain-facilitated semantic interoperability between multiple disparate systems of record (SORs) and related methods

A system for use with a plurality of systems of record (SORs) each including a respective database operating autonomously at an enterprise data layer based upon different respective database protocols and formats and comprising:

• a plurality of change monitors operating at an interop services layer to communicate with respective SORs using respective database protocols and formats, the change monitors configured to detect discrete Create-Retrieve-Update-Delete (CRUD) operations on their respective SORs related to at least one shared identity to generate an identity state change set corresponding to a current state of the at least one shared identity;
• a transactor operating at the interop services layer and communicating with the change monitors in a common domain language to transact the identity state change set, with associated metadata, to a distributed immutable long-term storage as a current transaction;
• a domain cache instance operating at a cloud data layer and cooperating with the distributed immutable long-term storage to propagate the identity state change set and associated metadata to recreate the current state of the at least one shared identity as of a time of the current transaction to at least one domain cache instance using the common domain language, the domain cache instance providing a transaction history including respective states of the at least one shared identity known to each of the SORs as of the time of each transaction in the transaction history;
• and
• a plurality of local state change alignment services each operating at a respective SOR and communicating with the domain cache instance in the common domain language, each local state change alignment service configured to communicate with the database of its respective SOR using the respective database protocol and format thereof and make available locally to the respective SOR the states of the at least one shared identity known to the other SORs at one or more points in the transaction history from the at least one domain cache instance.

A method comprising:

• operating a plurality of systems of record (SORs) each including a respective database operating autonomously at an enterprise data layer based upon different respective database protocols and formats;
• operating a plurality of change monitors operating at an interop services layer to communicate with respective SORs using respective database protocols and formats to detect discrete Create-Retrieve-Update-Delete (CRUD) operations on their respective SORs related to at least one shared identity to generate an identity state change set corresponding to a current state of the at least one shared identity;
• operating a transactor at the interop services layer for communicating with the change monitors in a common domain language to transact the identity state change set, with associated metadata, to a distributed immutable long-term storage as a current transaction;
• operating a domain cache instance at a cloud data layer for cooperating with the distributed immutable long-term storage to propagate the identity state change set and associated metadata to recreate the current state of the at least one shared identity as of a time of the current transaction to at least one domain cache instance using the common domain language, the domain cache instance providing a transaction history including respective states of the at least one shared identity known to each of the SORs as of the time of each transaction in the transaction history;
• and
• operating a plurality of local state change alignment services at a respective SOR for communicating with the domain cache instance in the common domain language and communicating with the database of its respective SOR using the respective database protocol and format thereof to make available locally to the respective SOR the states of the at least one shared identity known to the other SORs at one or more points in the transaction history from the at least one domain cache instance.