Is tamper proofing typically a feature of event sourcing systems? If so, how is it implemented?
Is tamper proofing typically a feature of event sourcing systems? If so, how is it implemented?
> Yes in the sense that event sourcing systems typically [are]... "append only"
However, I'd caution that this is not the same at all as cryptographic / blockchain style tamper proofing. I can still go into the database and change things myself, or create a new one altogether.
There are some interesting ideas in the article. I.e. making a peg to a blockchain, but that won't solve the throughput / trust dilemma.
https://en.wikipedia.org/wiki/Write_once_read_many#Current_W...
If you wanted to make your event stream more tamper-proof you could also introduce a merkle tree-like row which hashes the current event, the previous hash and a secret key. Any tampering of the data would need this key and would need to recompute future events.
It's still not perfect because with the key this is easy to do.