Harnessing the Power of Materialised Views in Cosmos DB
summary
Explains how Azure Cosmos DB uses Materialized Views (preview) to precompute and store query-specific documents, trading more expensive writes and storage for far cheaper, faster reads and fewer cross-partition queries. Shows implementation patterns using change feed + Azure Functions (output bindings and triggers), JSON/CLI deployment of view definitions, and alternatives for heavy processing like Apache Spark. Emphasizes partition-key design and RU cost math, and calls out current limits: no WHERE support in view definitions and no RBAC or CMK encryption for materialized views yet.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:01Azure Cosmos DB
- 6:32Account structure & partitioning
- 13:59Materialized views needed
- 18:40Change feed & event sourcing
- 24:05Materialized views benefits
- 28:44Demo: Azure Functions
- 32:01Built-in preview feature
- 33:51Limitations of feature
- 34:53Q&A
related talks
33mDriver for Data-Driven Change - Azure Cosmos DB Performance, Security & Cost Optimization Done Right
08mOptimize for the Best Cost and Performance for Azure Cosmos DB NoSQL API
45mGetting the Most from NoSQL in the Cloud with Azure Cosmos DB
18mIntelligent Resource Optimization: Mastering Azure Cosmos DB for Enterprise Workloads
28mArchitecture patterns of Azure Cosmos DB
01h 00mAzure Cosmos DB : A brief Note for Developers
48mPerformance tuning for Azure Cosmos DB
01h 00mCost cutting strategies for Azure Cosmos DB