Diagnosing and Resolving Azure Cosmos DB Provisioned Throughput Throttling (HTTP 429)
Learn how to spot Cosmos DB 429 throttling, map symptoms to causes, run ordered checks, apply fixes, and know when to escalate.
Loading…
ReadMeFeed / Community knowledge
#azure-cosmosdb
Real questions. Useful conversations. Find the people who know your stack.
Choosing the Right Azure Cosmos DB Consistency Level: A Practical Decision Guide
A concise decision guide for selecting Azure Cosmos DB consistency levels, balancing latency, cost, and data guarantees with a practical .NET example.
Enable and Consume Azure Cosmos DB Change Feed for Event‑Driven Processing
Learn how to turn Cosmos DB into an event source by enabling the Change Feed, setting up a lease container, and using the Change Feed Processor Library in C#. The guide covers configuration, validation, monitoring, and fallback strategies for reliable event handling.
csharpUsing Azure Cosmos DB Change Feed to Build Materialized Views for Multi‑Dimensional Queries
Learn how Azure Cosmos DB Change Feed can synchronize data into multiple containers, each partitioned for a different query pattern, to avoid expensive cross‑partition scans.
Using Azure Cosmos DB Change Feed with Azure Functions: Checkpointing Strategies and Trade‑offs
Learn how to reliably process inserts and updates from Cosmos DB using the Change Feed trigger, configure lease containers, handle deletes and schema changes, and avoid common pitfalls.
Choosing Session Consistency in Azure Cosmos DB for Low-Latency Real-Time Apps
Learn how Azure Cosmos DB's Session consistency level gives read-your-writes with latency close to Eventual, and see a .NET example that shows the trade-off and verification steps.
Configuring Least Privilege Access in Azure Cosmos DB Using RBAC and Customer-Managed Keys
When designing a secure Azure Cosmos DB deployment, it is important to limit permissions to only what each principal needs. How can I use Azure role-based access control (RBAC) to define fine‑grained permissions and combine that with customer‑managed keys for encryption‑at‑rest to achieve a least‑privilege configuration? Please outline the steps, any require