Handling GDPR with Apache Kafka: How does a log forget? | Confluent
Dec 8, 2017Ben Stopford

Summary
Introduces the use of Kafka's compacted topics as a mechanism for implementing GDPR's 'right to be forgotten'. Explains that messages can be marked for deletion by sending a new message with the same key and a null value. Discusses strategies for mapping data to keys, handling composite keys, and an alternative approach using per-user encryption keys. Also covers propagating deletes from originating databases via Kafka Connectors and provides tuning configurations for the log cleaner to control compaction timing and I/O.
More from the Kafka Infinite Storage trail
- Apache Kafka® vs Confluent Cloud: Latency Benchmarking Results
- Lowering Kafka Costs by Improving Utilization and Ease of Use
- Kafka Storage That’s 10x More Scalable and Elastic with Confluent
- Making Confluent Cloud 10x More Elastic Than Apache Kafka | Confluent Making Confluent Cloud 10x More Elastic Than Apache Kafka
- How Instacart Used Confluent to Scale 10 Years of Growth in 6 Weeks