To enable some more advanced real time / historical reporting it would be useful to store the history of events related to requests in the system as they are updated. Ideally we could look to push this out to a queue and update the database out of process, but for v1 it might be that this is done inline with the update code.
Ultimately we want to be able to show things such as a graph of events being opened / closed against a time series.
Longer term this might be fairly heavy load and dictate different data stores/processing method. For v1/vNext this is probably best kept within the current structure and data store.
To enable some more advanced real time / historical reporting it would be useful to store the history of events related to requests in the system as they are updated. Ideally we could look to push this out to a queue and update the database out of process, but for v1 it might be that this is done inline with the update code.
Ultimately we want to be able to show things such as a graph of events being opened / closed against a time series.
Longer term this might be fairly heavy load and dictate different data stores/processing method. For v1/vNext this is probably best kept within the current structure and data store.