Skip to main content

Menu

LEVEL 0
0/5 XP
HomeAboutTopicsPricingMy VaultStatsPractice TestsCertifications

Categories

🎓 Certifications
🤖 Artificial Intelligence
☁️ Cloud and Infrastructure
💾 Data and Databases
💼 Professional Skills
🎯 Programming and Development
🔒 Security and Networking
📚 Specialized Topics
CheatGrid
HomeAboutTopicsPricingMy VaultStatsPractice TestsCertifications
LVLEVEL 0
0/5 XP
GitHub
© 2026 CheatGrid™. All rights reserved.
Privacy PolicyTerms of UseAboutContact

Azure Cosmos DB Cheat Sheet

Azure Cosmos DB Cheat Sheet

Back to Databases
Updated 2026-04-21
Next Topic: Azure SQL Database and Managed Instance Cheat Sheet

Azure Cosmos DB is a globally distributed, multi-model database service designed for low-latency, elastic scale, and high availability. The core concepts that drive performance and cost are the resource model (accounts → databases → containers → items), partitioning, and throughput (RU/s). This cheat sheet focuses on the API for NoSQL (SQL query language) and the operational features you'll use most: indexing, consistency, search, change feed, backup/restore, and security. Full-text search and hybrid search reached general availability in 2025, making Cosmos DB a search-native database alongside its vector and transactional capabilities.


What This Cheat Sheet Covers

This topic spans 16 focused tables and 149 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Resource ModelTable 2: PartitioningTable 3: ThroughputTable 4: ConsistencyTable 5: Global DistributionTable 6: Query ClausesTable 7: FunctionsTable 8: IndexingTable 9: SearchTable 10: TransactionsTable 11: Change FeedTable 12: TTLTable 13: Backup and RestoreTable 14: SecurityTable 15: IntegrationsTable 16: Operations

Table 1: Resource Model

Everything in Cosmos DB nests in a strict hierarchy — accounts hold databases, databases hold containers, and containers hold the JSON items you actually read and write. Understanding where each thing sits is what makes the later topics (throughput, partitioning, indexing) click, since you provision and configure most features at the container level. The limits and emulator rows give you the hard numbers and the local sandbox you'll lean on while learning.

ResourceExampleDescription
Account
https://<account>.documents.azure.com:443/
Top-level Azure resource that provides the endpoint, authentication boundary, and global distribution settings for all databases/containers/items underneath.
Database
databaseId = "Sales"
• Logical namespace under an account that groups one or more containers
• throughput can be provisioned at database (shared) or container (dedicated) scope.
Container
containerId = "Orders"
• Unit of scalability for items, indexing, and throughput
• partition key is defined at creation and is immutable in-place.
Item
{ "id": "o-123", "customerId": "c-9" }
• JSON document stored in a container
• uniquely identified by the composite of (partitionKey, id) for the API for NoSQL.

More in Databases

  • Apache Cassandra Cheat Sheet
  • Azure SQL Database and Managed Instance Cheat Sheet
  • Amazon DynamoDB Cheat Sheet
  • Database Replication and High Availability Cheat Sheet
  • MariaDB Cheat Sheet
  • PostgreSQL Cheat Sheet
View all 42 topics in Databases