NoSQL doesn't mean No Schema
summary
Claim: NoSQL still has a schema and it belongs in code. Uses Python plus the jsonschema validator and BSON (Pongo) to embed a JSON Schema dictionary in a model class, raise exceptions on invalid instances, and run migration by introducing versioned classes and converting documents. Generates millions of documents to test performance (one aggregation once takes 15 minutes, prompting index or model changes). Outcome: validation and migration strategy works and prevents silent chaos. schema still exists json schema in code versioned class migrations
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:08What a schema really is
- 5:41SQL vs NoSQL schemas
- 8:11Schema in Python and NoSQL
- 13:36JSON Schema as metadata
- 16:47Use cases for schema design
- 21:44Data validation before insert
- 24:54CRUD with schema validation
- 27:45Schema migration strategies
- 33:01Schema must exist in code
- 37:08JSON validation limits
- 40:25Handling NoSQL updates
- 42:12Discipline in schema usage
- 43:20Sharing schema across apps
related talks
01h 01mNoSQL: An Analysis
18mFrom SQL to NOSQL - a gentle intro for Devs
53mThe NoSQL Store everyone ignores: PostgreSQL
34mNoSQL Database Cloud Service: Most flexible NoSQL Database
01h 02mDesign Good Schemas - Get a Better Database
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
46mFrom Tables to Documents -- Changing Your Database Mindset
45mNoSQL Data Modeling for Front-end Developers
