Keynote: Things Databases Don't Do (but should).
summary
Lists concrete features databases still don't handle: built-in soft deletes with retention, native tenant awareness for isolation/restore/geo placement, first-class change streams that push to S3/Kafka with consistent row-level permissions, and schema version control so migrations are tracked and reversible. Also missing are HTTP APIs with modern auth (OIDC/OAuth), easy multi-region data residency controls, and autonomous index/autotune that restructures indexes based on real access patterns. Watch if needing hands-on solutions or migration options for these gaps.
AI-written summary · about
chapters (11)
- 0:00Introduction and keynote setup
- 1:59Why databases don’t do everything
- 6:31Soft deletes and tenant awareness
- 8:18Tenant isolation challenges
- 12:58Capturing database changes
- 15:10Schema migrations and version control
- 19:04Query APIs and composability
- 21:59Modern protocols and authentication
- 25:08Global databases and compliance
- 29:22Intelligent workload tuning
- 32:09Summary and call to action
related talks
56mKeynote
35mAn Ode to 17 Databases in 39 minutes
35m10 things a developer should know about databases
34mData Storage: NoSQL Toasters and a Cloud of Kitchen Sinks
47mKeynote - The Evolving Role of Data in Software Development
32mCloud-Native Data: What is it? - Majors, Dunlap, O’Grady, Richardson, Drewitz
32mDatabases were not designed for this
30mThe database trends that are transforming your database infrastructure forever