Forum Discussion
Azure Cosmos Db Materialized View general availability
MicrosoftThanks for your question nitinrahim!
Materialized Views for NoSQL API is not GA yet and the timelines will depend on the feature asks from our customers. We are collating a list of use cases and we'll be happy to discuss about that.
As for the lag, yes - it is dependent on the provisioned RUs in the source and destination container as well as the SKU size provisioned for MV builder.
Talking about consistency, MVs are always eventually consistent. Irrespective of the consistency level set on your source, the MV containers will follow eventual consistency.
Thanks Abhinav.
Materialized view would be a good fit for the Customers considering we will have cross partition searches. We were thinking of having the materialized view to suffice the cross partition queries and have the load and point read on the base container and queries against the materialized view and split the RU's allocated between the same so the load/point read and queries are segregated. Synapse Link is not a good fit in our case considering the concurrency requirements and latency requirement. However we do need RBAC Support and Customer managed key support for materialized view as well considering the security requirements and nature of data of the Customer. If these requirements can be incorporated materialized view is a great fit as it simpler to manage than change feed feature and if its GA available Customers will incorporate the same.