K9db: Privacy-Compliant Storage For Web Applications By Construction
summary
K9db is a MySQL‑compatible database that enforces GDPR-style access and deletion by construction: developers add a few schema annotations and K9db builds a data ownership graph and generates procedures to find and delete all owned rows. Storage organizes rows into per-user microdatabases, stores shared rows in multiple owners' stores, and deletes user keys to render backups unreadable. Prototype covers 10 real apps, matches or exceeds MariaDB latency on reads, incurs modest state growth and encryption write overhead.
AI-written summary · about
chapters (9)
- 0:00K9DB introduction
- 1:32User data deletion challenges
- 3:59Building K9DB challenges
- 4:44Data Ownership Graph
- 7:27Ownership rules enforcement
- 9:15Ownership-aware storage policies
- 12:26Performance and compliance optimizations
- 13:09K9DB performance evaluation
- 15:35Conclusion and future
related talks
19mPrivate DBaaS: Why you Need it, How to Build It
24mgives databases to everyone
59mDatabase Encryption in a GDPR World
01h 02mRonDB: A Key-Value Store with SQL Capabilities and LATS Properties
40mKalDB: A cloud native log search platform
19mBuild Global-Scale Apps Using Globally Distributed Autonomous Databases
31mFast, highly effective database security using searchable encryption (without the yak shave)
39mdev.privacy: GDPR in a nutshell