Because XTDB uses a transaction log and document store, it's possible to purge a document from the document store so that the only thing that remains is an irreversibly hashed document id on the transaction log. This isn't crufty. Using a reference like this is a very common, good solution to GDPR compliance.
A system that's truly immutable in all parts is elegant, but unfortunately the real world is not as easily modelled. Being able to truly expunge data is actually needed at times. And it's not just GDPR. What happens when something truly sensitive is written to an immutable store?
I'd like to be able to know my data was purged, but still...
Comments
Because XTDB uses a transaction log and document store, it's possible to purge a document from the document store so that the only thing that remains is an irreversibly hashed document id on the transaction log. This isn't crufty. Using a reference like this is a very common, good solution to GDPR compliance.
A system that's truly immutable in all parts is elegant, but unfortunately the real world is not as easily modelled. Being able to truly expunge data is actually needed at times. And it's not just GDPR. What happens when something truly sensitive is written to an immutable store?
So do you want the feature or not?! :)