Note that as of Oct 2021, Dedicated gateway is only available for a "Core (SQL)" account. Not for MongoDB. It could be helpful to mention that before charging ahead with the demo.
Any Updates on Gremlin? Performance is kinda poor :( Will the upcoming "cache" Option also be available for Gremlin? In the End it uses the SQL Core API or? So Gremlin is converted to SQL not?
I have few queries on Azure cosmos integrated cache. 1. In my case, I have several containers in Cosmos DB and only 1 or 2 out of them have reference data and are suitable for point read and repeatable queries, So If I enable dedicated gateway for my Azure cosmos DB account, and configure the point read operations and queries for just the reference data containers , then what will happen to the remaining containers where I don't need the caching, Will the requests to them also go through dedicated gateway and also will incure slight overhead in latency. 2. How I can make sure that I use Integrated caching for limited 1 or 2 containers and by default all remaining containers (which are not suitable for caching) should go through direct mode and will not have low latency. 3. I see Bypass the integrated cache is in (Preview) but i don't understand if there is need to explicitly bypass everything which is not suitable for caching. Since my caching need is only for some containers, so it should be only for those where i have configured point reads and queries explicitly.
Hi there, thanks for your patience on this! The Azure Cosmos DB dedicated gateway is provisioned at the account level and all requests from Cosmos clients in Gateway mode configured with the dedicated gateway connection string will be routed through the dedicated gateway. You can set the bypass integrated cache request option to control which of these requests use the integrated cache, however they are still routed through the dedicated gateway itself. Each Cosmos client can be configured to use its own connection string. If one application has a workload that lends itself well to caching and another application doesn’t, you can configure the dedicated gateway connection string for the first application and the standard Azure Cosmos DB connection string with direct mode for the second application. If the same application needs to use the dedicated gateway with integrated cache for some containers and direct mode for other containers, you can create two Cosmos clients with different configurations in the same application. Please note, it’s generally recommended to create each Cosmos client as a singleton, and creating multiple Cosmos clients in a single application should be done sparingly.
@@MicrosoftAzure If I have a single cosmos db account and enable dedicated gateway mode on that account, will I still be able to use 2 different connection strings i.e direct mode for non cache containers and dedicated gateway connection strings for cache items containers ?
Yes, when the dedicated gateway is provisioned for an account you can choose to use either the dedicated gateway connection string or the standard connection string. Connectivity mode is independent of connection string, meaning that you can choose either Direct or Gateway mode connectivity with either connection string. Each Cosmos client must use one connection string and one connectivity mode. If a single application needs to use the standard connection string with Direct mode for some containers and the dedicated gateway connection string with Gateway mode for other containers, you will need to create two Cosmos clients in that application. You can learn more about configuring you application to use the dedicated gateway here: msft.it/6055iv5xN
@@MicrosoftAzure that means 2 different cosmos db accounts. 1 account with containers with caching workload having dedicated gateway mode. Another account with containers with non caching (update workloads) with direct mode ? How consistency will be handled with 2 cosmos db accounts as I have a single distributed we application
You can create multiple Cosmos clients with different configurations for a single Cosmos account. There’s no need to create multiple Azure Cosmos DB accounts to use both Direct and Gateway mode. Please refer to this document for an example of configuring a Cosmos client in .NET (there are similar docs for other languages as well): msft.it/6056ivLcs
