Here is a diagram that illustrates integrating the blockchain network to an operational data store:

Oftentimes, organizations are looking at ways of running analytics on the information from their ledgers. However, issuing multiple/large queries against the organization's peers will only impact the online performance of the system. Generally, the recognized approach in enterprise system design is to move the data to an operational data store. The data can then be easily queried. Additional views on the data can be created by enriching the data using different data sources.

In this pattern, the event listener subscribes to the Fabric organization events. As such, it can receive transactions from all channels the organization is entitled to. If the preservation of the data's integrity is important, the event listener can calculate a hash of every record and store them alongside the records.

You will notice that the pattern also accounts for a syncAll function that would allow the event listener to re-synchronize the data store with the latest view of the world state. Keep in mind that the implementation of this syncAll function will need to be done carefully and will most likely require that the function supports the pagination of the resultsets.