cosmosdb-datamodeling

Design Azure Cosmos DB NoSQL data models from application requirements.

Updated May 16, 2026
One-click install
npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill cosmosdb-datamodeling-p-o-ke-nae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cosmosdb-datamodeling
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/cosmosdb-datamodeling
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill cosmosdb-datamodeling-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn application requirements into a practical Azure Cosmos DB NoSQL data model, reducing guesswork around partitioning, aggregation, indexing, and container design.

Core Features & Use Cases

  • Requirement Discovery: Captures the domain, entities, scale, and access patterns needed before designing the database.
  • Aggregate and Container Design: Evaluates when to use single-document, multi-document, or separate-container approaches for related data.
  • Cosmos DB Optimization: Guides partition key selection, indexing strategy, throughput planning, and hot partition mitigation.
  • Use Case: A backend team can use this Skill to document an API workload, analyze reads and writes, and produce a reasoned Cosmos DB model for implementation and review.

Quick Start

Ask the skill to gather your Cosmos DB application details and produce a step-by-step NoSQL data model proposal for your workload.

Frequently Asked Questions about cosmosdb-datamodeling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an Azure Cosmos DB NoSQL data model from application requirements?

To design an Azure Cosmos DB NoSQL data model, you must first gather domain entities, workload scale, and access patterns, then determine aggregate boundaries, partition keys, and indexing strategies to produce a reasoned container design.

What is the best way to choose a partition key for Cosmos DB NoSQL containers?

Choosing a Cosmos DB partition key requires analyzing your application's read and write access patterns to evenly distribute workload scale and mitigate hot partitions across your NoSQL containers.

When should I use single-document aggregates versus separate containers in Cosmos DB NoSQL?

Decide between single-document or separate-container aggregates in Cosmos DB by evaluating your application access patterns to optimize read and write efficiency for related data.

Does this NoSQL data modeling approach work for operational workloads and APIs?

Yes, this NoSQL data modeling approach supports operational workloads and APIs by documenting read and write patterns, throughput planning, and indexing decisions to produce a practical Azure Cosmos DB container design.

Why does indexing strategy matter in Azure Cosmos DB data modeling?

Indexing strategy matters in Azure Cosmos DB data modeling because it directly impacts query performance and throughput planning for specific application read and write access patterns.

What are the limitations of NoSQL data modeling for high-scale operational workloads in Cosmos DB?

NoSQL data modeling for high-scale operational workloads in Cosmos DB faces limitations like hot partition mitigation and aggregate boundary selection, requiring careful access-pattern analysis to avoid performance bottlenecks.