I’m looking at the query store configuration options, and I’d like to know a bit more about how it works and any important points we should be aware of to ensure accurate responses from the json-api.
In our case, for example, we will have an automated service watching for external events, and then exercising choices on the ledger in response. This means a contract of this template could be queried for, and then it could be archived and created with updates 0.3 seconds later, how will the query store react to this? The given choice may archive and create a couple of other related contracts, how heavy could the traffic be between the query store and the ledger in this sort of scenario? Could there be performance implications?
Given that this query store is recommended for production use cases it would be great to see more documentation than the small paragraph that is currently present.
Thanks in advance!