← Graph

Three Ways To Delete User Data In Event-Sourced Systems

takeaway 3 connections

Davydov surveys three approaches to deleting user-related data from an immutable event store: (1) Martin Fowler's reactive approach (not explained in depth); (2) encrypt sensitive payloads per-user and lose the decryption key; (3) compact the affected events out, Kafka-style (acknowledged as 'not a true way'). The Q&A adds a fourth blockchain-industry idea: store payloads separately from events, keep only fingerprints inside events to preserve immutability proofs, and delete the payload on request.

type
recommendation
takeaway Three Ways To Delete User Data In Event-Sourced Systems
about
Event Sourcing concept
Approaches apply specifically to event-sourced systems.
takeaway Three Ways To Delete User Data In Event-Sourced Systems
about
Martin Fowler person
Cites Martin Fowler as source of the reactive approach.
takeaway Three Ways To Delete User Data In Event-Sourced Systems
from_talk
Advising section on GDPR-style deletion strategies.

Provenance

Read by
1 extraction