JSON Data Modeling
summary
Explains concrete modeling choices for JSON with Couchbase: embed when an entity owns related data, refer when many-to-many or frequent writes, prefer consolidation until document size hits limits (mentions 20 MB document limit and Cosmos ~2 MB); use key-value for microsecond lookups and the subdocument API to update parts without transferring whole documents; SQL++ and built-in search (Blevy) enable joins and full-text queries; recommends cooperative re-versioning, tools like Hackolade/Erwin/jsoneditoronline.org, and trying Capella via couchbase.live for quick experiments.
AI-written summary · about
chapters (4)
- 0:00Start
- 5:26Making the Same Change With a Document Database
- 38:20Summary
- 42:58Versioning approach 1: Version Numbers
related talks
59mData Modeling for
01h 02mNext Generation Data Storage with CouchDB
26mNoSQL Data Modeling for Front-end Developers
55mData Modeling in a Non-Relational World
45mNoSQL Data Modeling for Front-end Developers
44mThe Developer's Guide to Data Modelling with Document Databases
25mAzure Cosmos DB Modeling Methodology
46mFrom Tables to Documents -- Changing Your Database Mindset
