Question 1104

The Log Never Forgets

User events land in an append-only event log whose archived segments are written to object storage and never expire. A user submits an erasure request. Which design lets you honor it without rewriting history?

A

Set a deletion flag on the row in the downstream user table and leave the archived event payloads in object storage exactly as they are

B

Encrypt each user's event payloads under a key unique to that user and destroy the key on request, leaving unreadable ciphertext in place

C

Rewrite the archived segments in place with that user's events removed, then repoint the offsets of every consumer group that had already read past them

D

Cut the retention window to twenty four hours for the whole topic so historical events for every user age out of the archive quickly