How De-normalizing Your Data with JSON Can Boost Query Performance
summary
Argues that denormalizing into JSON columns and using MySQL Document Store plus the X Dev API cuts the number of costly joins, keeps frequently changing or rare fields mutable, and still allows indexable JSON fields via generated columns. Demonstrates a bulk loader ingesting 25,000 records in ~2s, shows JSON_TABLE for analytics, and reports typical query overhead of only three to four percent versus fully normalized schemas while preserving the ability to normalize hot fields later.
AI-written summary · about
chapters (44)
- 0:00Introduction
- 0:27History Lesson
- 0:59The Problem
- 1:40The Solution
- 1:58Tape Drives
- 2:28Single Key
- 2:49Edgar Codd
- 3:10Structured Query Language
- 3:38Better Performance
- 3:58Normalizing Data
- 4:34Cost Model
- 5:15Package Your Data
- 5:54No SQL
- 7:25SQL Vendors
- 8:12JSON Data Type
- 8:54Creating a Springless Fantasy Business
- 9:20Guitars
- 9:58Custom Guitars
- 10:15Classic Guitars
- 11:01Getting Started
- 11:11Serial Number
- 12:39Electric Guitar
- 12:58Wiring Options
- 13:24Variable Options
- 13:38Finite Element Analysis
- 13:59ManytoMany Join
- 14:29JSON Data Types
- 14:49JSON mutable
- 15:28Production data
- 15:50Schema list JSON
- 16:22Architecture
- 17:46New Shell
- 19:05New API
- 19:26Search Conditions
- 19:45New JSON API
- 20:15New JSON API with Tables
- 20:41JSON Table
- 22:01SQL Operator
- 22:39JSON Bulk Loader
- 22:55Hybrid Databases
- 23:10NonHybrid Databases
- 23:48Data Structure Changes
- 24:52Buy my book
- 25:11Questions
