You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There are many examples that recommend creating a CosmosClient instance using the Builder pattern (it is also easier to read and understand). However, the solution to the cold start problem mentioned here #1706 isn't ported over to this pattern.
Describe the solution you'd like
The Builder has a new method (or an overload) that takes in the containers to be initialized. My personal recommendation is to also provide an option to pre-load everything in the account rather than having to list every database and container.
Describe alternatives you've considered
We recently came across an issue where the initial latencies for calls jumped to 40 seconds or more. My current alternative is to get rid of the builder pattern and create the clientOptions directly and use the CreateAndInitializeAsync method. However, I feel that's a letdown and the solution should be ported over to the Builder class.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There are many examples that recommend creating a CosmosClient instance using the Builder pattern (it is also easier to read and understand). However, the solution to the cold start problem mentioned here #1706 isn't ported over to this pattern.
Describe the solution you'd like
The Builder has a new method (or an overload) that takes in the containers to be initialized. My personal recommendation is to also provide an option to pre-load everything in the account rather than having to list every database and container.
Describe alternatives you've considered
We recently came across an issue where the initial latencies for calls jumped to 40 seconds or more. My current alternative is to get rid of the builder pattern and create the clientOptions directly and use the CreateAndInitializeAsync method. However, I feel that's a letdown and the solution should be ported over to the Builder class.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: