Enhancing Data Ingestion and Enrichment at Aware with Azure Cosmos DB
summary
Aware uses Azure Cosmos DB with KEDA autoscalers and change feeds to ingest and enrich message streams, capturing data at ingest, triggering transforms and ML enrichments, and storing results in Cosmos collections. Partition key choice and hot-partition fixes drive schema changes; logging RU per query and a 10% reservations rule prevent wasted capacity. Throttles (HTTP 429) lead to workload smoothing rather than immediate cluster scale-up. Data store doubles with no read/write latency increase and moves from dozens of per-customer DBs to a handful of global instances.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:27Business problem overview
- 1:31System architecture
- 2:57Why Cosmos DB
- 3:59Ingestion pipeline switch
- 4:42Partitioning strategies
- 5:47Query tuning
- 6:08Change feeds
- 7:33Reservations and autoscaling
- 8:41Monitoring and logging
- 9:23Migration results
related talks
01h 03mData Modeling and Partitioning in Azure Cosmos DB
32mAzure Cosmos DB Performance Tuning - Sonal Pathak & Amresh Krishanmurthy
48mPerformance tuning for Azure Cosmos DB
01h 02mAzure Cosmos DB - Low Latency and High Availability at Planet Scale
18mIntelligent Resource Optimization: Mastering Azure Cosmos DB for Enterprise Workloads
33mDriver for Data-Driven Change - Azure Cosmos DB Performance, Security & Cost Optimization Done Right
01h 00mCost cutting strategies for Azure Cosmos DB
23mServing Customer Data with Azure Cosmos DB
