Cosmos DB Modeling Methodology
summary
Methodology converts a 300+ table legacy e commerce schema into Cosmos DB by mapping DDD aggregates to containers and then optimizing for queries and partitions. It uses SQL API document models, follows rules like each aggregate → one container and anchor primary key as partition key, maps non‑root entities to distinct document types, embeds value objects unless they change or are many, uses a dedicated dictionary container, references across aggregates, duplicates orders into accounts to avoid cross‑partition queries and tunes indexes and partition sizes.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:58Importance of modeling in NoSQL
- 2:02Case study: legacy e-commerce platform migration challenge Scaling issues related to support bigger number of Relational Tables simultaneous users from around the globe
- 4:41Methodology inspiration
- 7:04The methodology: executive summary
- 11:51Case study: application flow
- 15:04Case study: DDD aggregates
- 16:23Data realities & queries statistics
- 17:49Mapping rules. Part 3
- 20:22Case study: logical data model
- 23:32Case study: physical optimization
related talks
01h 03mData Modeling and Partitioning in Azure Cosmos DB
01h 00mAzure Cosmos DB : A brief Note for Developers
48mJSON Data Modeling
13mHow to do Data Modeling for Distributed Postgres in Azure Cosmos DB
57mCosmosDB 101: Basics and quickstart
01h 01mFrom SQL to Azure Cosmos DB
50mAzure Cosmos DB - Technical Deep Dive
01h 02mFrom SQL to Azure Cosmos DB
