Data Modeling: Master This Critical Step to Adopting a Distributed Database
summary
Explains concrete rules for YugabyteDB data placement and tradeoffs: pick primary key partition columns to co-locate rows (example: store_id partitioning vs product_id), use secondary and covering index to make reads finish in one RPC (demo: index including in_store_count returns stores for a product in a single network round trip), avoid global sequences and prefer uuid over sequences for uniqueness, accept extra update cost for cross-node indexes, and denormalize bounded children or enums to eliminate joins; YCQL offers static objects, YSQL is regular SQL.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:35Data Model and Your Application Use Patterns
- 3:51Rules of Thumb
- 7:06Primary Key Selection
- 7:43Sequence Numbers
- 13:07Gigabyte Indexes
- 15:58Denormalization
- 18:29Data Duplication
related talks
29mData Modeling for Distributed SQL
33mMigrating from Oracle to
27mIntroduction to YugabyteDB – Design and Architecture
27mIntroduction to YugabyteDB: Design and Architecture
29mScalable Product Mappings
47mAnatomy of a Distributed SQL Database - YugabyteDB
30mBuilding Cloud Native Applications on Distributed SQL Platform
26mIntroducing YugabyteDB for PostgreSQL Users
