Cosmos DB Geo-replication - SQL on the edge episode 14

• Reducing read latency: you can place read copies of the database close to users locations.
• Graceful DR Degradation: if you have multiple geo-replicated regions you can set priorities to failover first to a region close to your main user base, then another a bit further and so on.
• Data Sovereignty: Cosmos DB offers geo-fencing by allowing the user to specify the failover regions. For example, if your data is not allowed to leave Canada, then you can setup your database to only permit failover between Canada Central and Canada East. This way, even in the event of a disaster, you know that you are compliant with your regulatory requirements.

// create a connection policy object
 
 ConnectionPolicy connectionPolicy = new ConnectionPolicy();
 
 //set the proper regions
 connectionPolicy.PreferredLocations.Add(LocationNames.CanadaCentral); // first preference
 connectionPolicy.PreferredLocations.Add(LocationNames.CanadaEast); // second preference
 
 // initialize connection with your endpoint, your access key and the policy object we just created
 DocumentClient docClient = new DocumentClient(
  https://mycosmosdb.documents.azure.com:443/,
  "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  connectionPolicy);
 
 // test the connection
 await docClient.OpenAsync();