ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #cosmosdb
Stop polling your database for updates. Learn how to use the Cosmos DB Change Feed to build event‑driven, real‑time data pipelines with a concrete Azure Functions example.
The change feed is always on for SQL API containers, so the real work is designing for per-partition ordering and at-least-once delivery. Here is a concrete Azure Functions setup and how to verify it.
Learn how to use the Azure Cosmos DB Change Feed and Change Feed Processor to build event-driven materialized views and implement CQRS patterns for high-performance reads.
Learn how to enable and consume Cosmos DB Change Feed in a minimal, secure design. Covers requirements, trust boundaries, monitoring, failure modes, and when to scale.
A single partition key like /tenantId breaks down when one tenant outgrows 20 GB. Hierarchical partition keys in Cosmos DB fix that — if your queries filter top-down. Here's how to choose and verify.
Objective Determine whether point-in-time restore operations maintain data consistency when the source Cosmos DB account undergoes API version transitions within the 4-week backup retention window. Constraints Core SQL API accounts support continuous backup and PITR features. The restore creates a new container with copied data preserving schema but not iden
The goal is to understand whether Cosmos DB Change Feed guarantees exactly‑once processing of pre‑upgrade changes when a move to API v2.0.0 Full Fidelity mode fails and the account reverts to the legacy API. Constraints include the lack of automatic checkpoint migration during version changes, the possibility that a processor already switched to Full Fidelit
Automatic indexing in Azure Cosmos DB for NoSQL indexes every property on write, simplifying schema evolution but consuming request units per operation. When a custom indexing policy excludes specific paths, the default composite index interaction with remaining fields becomes a design consideration, particularly for range and equality queries. The policy ch
Goal Determine whether Cosmos DB can automatically revert writes that succeed before a schema validation rule change but become invalid after the change, without requiring application‑level compensation. The container‑level JSON schema validation is enforced at write time, and while TransactionalBatch provides atomicity across documents, a schema modificatio
azure