azure-cosmosdb

Azure Cosmos DB performance optimization and best practices guidelines for NoSQL, partitioning, queries, and SDK usage. Use when writing, reviewing, or refactoring code that interacts with Azure Cosmos DB, designing data models, optimizing queries, or implementing high-performance database operations. USE FOR: Cosmos DB NoSQL, partition key design, RU optimization, point reads, cross-partition queries, SDK singleton, CosmosClient, container modeling, change feed, bulk operations, vector search, full-text search, hierarchical partition keys, global distribution, autoscale throughput, indexing policy. DO NOT USE FOR: PostgreSQL, MySQL, MongoDB (non-Azure), DynamoDB, Cassandra, Azure SQL, Cosmos DB for PostgreSQL (vCore), Cosmos DB for MongoDB vCore, Azure DocumentDB, general SQL databases, Redis, Elasticsearch.

Azure Cosmos DB data modeling best practices: embedding vs referencing, document size limits, schema versioning, type discriminators, JSON serialization, denormalization, and relationship patterns. USE FOR: Cosmos DB document design, embedding related data, referencing large data, 2MB item limit, nesting depth, numeric precision, denormalize reads, schema versions, type discriminator, polymorphic containers, JSON serialization, relationship references. DO NOT USE FOR: partition key design (use cosmosdb-partition-key), query optimization (use cosmosdb-query-optimization), SDK client code (use cosmosdb-sdk).

Azure Cosmos DB design patterns: change feed materialized views, efficient ranking, service layer relationship hydration, LangGraph multi-agent orchestration, human-in-the-loop interrupts, checkpoint resumption, agent routing, FastAPI startup, chat history separation, background task writes, async Cosmos DB routing, and agent name attribution. USE FOR: Cosmos DB change feed, materialized views, CQRS, event sourcing, ranking patterns, service layer, relationship hydration, LangGraph, multi-agent, human-in-the-loop, interrupt, checkpoint, agent routing, FastAPI startup, chat history, background tasks, async routing, agent attribution, AI grounding. DO NOT USE FOR: SDK configuration (use cosmosdb-sdk), data modeling (use cosmosdb-data-modeling).

Azure Cosmos DB full-text search best practices: enabling the capability flag, defining fullTextPolicy, configuring fullTextIndexes, keyword matching with FullTextContains functions, BM25 relevance ranking, and hybrid queries. USE FOR: Cosmos DB full-text search, FTS, EnableNoSQLFullTextSearch, fullTextPolicy, fullTextIndexes, FullTextContains, FullTextContainsAll, FullTextContainsAny, FullTextScore, BM25 ranking, RANK, hybrid queries, keyword search, inverted index, language-aware tokenization. DO NOT USE FOR: vector search (use cosmosdb-vector-search), regular query optimization (use cosmosdb-query-optimization).

Azure Cosmos DB global distribution best practices: multi-region writes, consistency levels, conflict resolution, automatic failover, read regions, and zone redundancy for high availability. USE FOR: Cosmos DB multi-region, consistency levels, strong consistency, bounded staleness, session consistency, eventual consistency, conflict resolution, automatic failover, read regions, zone redundancy, global replication, disaster recovery, geo-redundancy, multi-master. DO NOT USE FOR: SDK preferred regions (use cosmosdb-sdk), monitoring (use cosmosdb-monitoring).