Change Feed is a core Cosmos DB feature that enables event-driven patterns, but there is no dedicated rule on how to properly set up and configure a Change Feed processor (as opposed to the materialized views pattern we already cover).
We need a rule covering:
- Processor setup with lease container
- Start from beginning vs. start from now
- Error handling and poison message strategies
- Scaling with multiple instances
- Lease expiration and load balancing
Category: \pattern-\ Design Patterns
Impact: High
Suggested file: \skills/cosmosdb-best-practices/rules/pattern-change-feed-processor.md\
References:
This is a good first issue! Follow the Contributing Guide and use the rule template to get started.
Change Feed is a core Cosmos DB feature that enables event-driven patterns, but there is no dedicated rule on how to properly set up and configure a Change Feed processor (as opposed to the materialized views pattern we already cover).
We need a rule covering:
Category: \pattern-\ Design Patterns
Impact: High
Suggested file: \skills/cosmosdb-best-practices/rules/pattern-change-feed-processor.md\
References:
This is a good first issue! Follow the Contributing Guide and use the rule template to get started.