Avoiding the Kitchen Sink Database

on YouTube ↗05m

" summary

Claims that splitting storage into a separate canonical store for critical user data and a UI cache database for derived, display-focused fields fixes migration, backup and sync pain while letting the UI optimize for responsiveness. Implements a change controller that listens to canonical changes and refreshes derived rows. Applied successfully to two apps, powers search indexes thumbnails and continuous PDF generation, and reduces migration complexity at the cost of managing two data stores.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 0:23App Architecture
3. 0:33Proven Track Record
4. 2:09Actual Data

" related talks

• 31mHow Kurtosys Ditched Its Legacy Database To Drive The Future Of Investment ManagementSunil Odedra, Sukki Sandhar · Big Data LDN 2022
• 43mCaching and Beyond - Smarter Data Processing with JavaChristian Kuemmel · JCON EUROPE 2026
• 37mKEYNOTE: Data Architecture Turned Upside DownHannes Mühleisen · PyData Amsterdam 2025
• 01h 04mHow do you store your data?Artem Orobets · JavaDay Kiev 2014
• 41mDo you really need that relational DB?Donatas Aleksandravičius · Dutch PHP Conference 2019
• 46mKEEPING UP IN A DATA-INTENSIVE WORLD WITH SINGLESTOREJordan Tigani · Crunch Conference 2021
• 25mMigrating DatastoresTessa Bradbury · SREcon22 Asia/Pacific
• 27mHow Micro-Service Patterns Change When the Database ScalableBrecht De Rooms · Scale By the Bay 2020