Q:

Can I have more than one consistency model for documentDb collection? 

We have a web application which talks to microservices hosted in service fabric cluster (which means a given service can be hosted on more than one node).  The microservices talk to documentDb collections.  Lets say we have one service talks to a distinct collection.  We have batch processing which also leverage some of these microservices. 
We would like to follow strong consistency model for UI related requests in our microservices so that users are not surprised by the results.  Since non-sql database performs best with eventual consistency, we would like to use eventual consistency for batch processing. 

Is it possible to choose eventual consistency at collection/account level in documentDb? 
With (1), can I also choose strong consistency for my UI operations (from microservices)? 

We are only looking for a condition where both (1) and (2) are true at the same time. 
If both (1) and (2) are possible at the same time, how would I go about it? 

A:

Thanks Raghu 
Yes.,  It is already supported. 
You can relax consistency at individual request level and use Strong for UI(default).  
For setting the consistency at request level - kindly see - https://msdn.microsoft.com/en-us/library/azure/microsoft.azure.documents.client.requestoptions.consistencylevel.aspx#P:Microsoft.Azure.Documents.Client.RequestOptions.ConsistencyLevel 

