I am exploring some concepts around using Influx as an immutable datastore for a few different use cases. There are some scenarios in manufacturing where this could be an attractive feature.
Two concepts come to mind and I wanted to check to see if others had created or are working on similar solutions.
The first level of “protection” would be to disallow writing any value that precedes the latest entry. Said another way, don’t allow insertion or update of any “old” data. I speculate a window would need to be defined for what “old” data is. I have reviewed the configuration file and I can’t seem to find any obvious methods for implementing this restriction.
The second level of “protection” might involve something along the lines of calculating a hash of a data file once it is written to disk and all compaction and other maintenance are complete. This hash would then be persisted to an alternate storage location that is also immutable. Yes, maybe blah blah blockchain but that’s a detail of implementation. Now this hash can be used to verify the integrity of the data file.
Curious if anyone else has solved one or both of these challenges or if you are working on these.