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
  1. A change-feed processor with appropriate lease and checkpoint state
  2. A loop that deletes progress after every read
  3. A public DNS zone as the checkpoint store
  4. A fixed random delay with no progress tracking

Comments — 0