ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to decouple your Azure Cosmos DB writes from downstream processing using the Change Feed and Change Feed Processor (CFP) to build scalable, event-driven architectures.
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.
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
cosmosdb