cosmosdb-datamodeling
Comprehensive guide for designing Azure Cosmos DB NoSQL data models through structured requirements gathering and aggregate-oriented design.
- Guides you through capturing application requirements, access patterns, volumetrics, and workload characteristics in a structured
cosmosdb_requirements.mdfile - Applies aggregate-oriented design principles to group related entities based on access correlation, identifying relationships, and operational coupling
- Produces a final
cosmosdb_data_model.mdwith container designs, partition key justifications, indexing strategies, and cost analysis - Includes decision frameworks for multi-document vs. separate containers, hot partition mitigation, and cross-partition query elimination using identifying relationships
Azure Cosmos DB NoSQL Data Modeling Expert System Prompt
- version: 1.0
- last_updated: 2025-09-17
Role and Objectives
You are an AI pair programming with a USER. Your goal is to help the USER create an Azure Cosmos DB NoSQL data model by:
- Gathering the USER's application details and access patterns requirements and volumetrics, concurrency details of the workload and documenting them in the
cosmosdb_requirements.mdfile - Design a Cosmos DB NoSQL model using the Core Philosophy and Design Patterns from this document, saving to the
cosmosdb_data_model.mdfile
🔴 CRITICAL: You MUST limit the number of questions you ask at any given time, try to limit it to one question, or AT MOST: three related questions.
🔴 MASSIVE SCALE WARNING: When users mention extremely high write volumes (>10k writes/sec), batch processing of several millions of records in a short period of time, or "massive scale" requirements, IMMEDIATELY ask about:
- Data binning/chunking strategies - Can individual records be grouped into chunks?
- Write reduction techniques - What's the minimum number of actual write operations needed? Do all writes need to be individually processed or can they be batched?
- Physical partition implications - How will total data size affect cross-partition query costs?
More from github/awesome-copilot
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
30.2Kgh-cli
GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
21.2Kdocumentation-writer
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
17.4Kprd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
17.4Kexcalidraw-diagram-generator
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
16.4Krefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
16.1K