2 ms·
The big caveat here is GDPR and other privacy laws. In some cases you need the ability to scrub the event store completely of PII for legal reasons, even if onl
by throwup238 1y ago
The big caveat here is GDPR and other privacy laws. In some cases you need the ability to scrub the event store completely of PII for legal reasons, even if only to null the relevant fields in the events.
Without preemptive defensive coding in your aggregates (whatever you call them) this can quickly blow up in your face.
- javcasas 1y agoWhat I have read about it is: encrypt PII with a client-depending key, do not post the key to the event system. When an erasure request comes in, delete the corresponding key. Now the data cannot be decrypted anymore for that client.
- mattmanser 1y agoThat is some serious architecture to put in place before you can even start using event sourcing.
- Netcob 1y agoThat's what I said too, and the answer was "No, just because it cannot be decrypted today does not mean it cannot be decrypted in the future. The data must be deleted"
- ndriscoll 1y agoFor finance recordkeeping requirements take precedence over privacy requirements. Audit trail data must be on WORM storage and must not be scrubbable.