CODEWITHSUNDEEP
azure-cosmosdb
Peter Friend
Peter Friend

Reputation: 780

How does CosmosDB change feed behave in the presence of multi-master replication?

I have CosmosDB set up in multi-master mode replicated to several sites, and am utilizing the change feed API to read updates from the database. Currently I am reading from a single location, but soon I plan to read from multiple for failover redundancy. What isn't clear is how the change feed API is supposed to behave in this scenario. If the timestamp that change feed uses to poll for changes is copied directly from the originating site, I can imagine some timing situations where change feed would not see the changes since the Continuation Token is already in the future. I wouldn't expect any problems if the timestamp is updated on the replicated site. While I can test this myself to verify, I would prefer to know what is explicitly supported by the CosmosDB team.

Upvotes: 1

Views: 314

Answers (1)

Matias Quaranta
Matias Quaranta

Reputation: 15603

All changes that happen in all regions are replicated to each region's Change Feed, so you should be able to read the Change Feed from any of the regions and obtain all the changes without issues.

Upvotes: 1

Related Questions