This website uses cookies to ensure you get the best experience.
Learn more.
A service reacts to new or updated Cosmos items. It scales the processor across workers and must resume after failures. What should be configured?
Published
- A change-feed processor with appropriate lease and checkpoint state
- A loop that deletes progress after every read
- A public DNS zone as the checkpoint store
- A fixed random delay with no progress tracking
Comments — 0
Sign in to comment