| Multi-Model API Selection (NoSQL/SQL vs MongoDB vCore vs Cassandra) | Audits query access patterns and wire-protocol compatibility to choose NoSQL (Core SQL) for global scale, MongoDB vCore for native aggregation pipelines, or Cassandra API, avoiding costly multi-API architectural dead-ends. | Defaults to classic Cosmos MongoDB API for all legacy migrations, encountering aggregation operator feature gaps and RU billing penalties. | Treats Cosmos DB as a drop-in relational database replacement, porting normalized tables directly without evaluating NoSQL document hierarchies. | Selects APIs based on familiar SDK syntax without auditing underlying indexing semantics, partition boundaries, or RU cost models. |
| High-Cardinality Logical Partition Key Modeling (20GB Boundary Control) | Models high-cardinality synthetic and compound partition keys, enforcing strict 20GB physical partition boundaries and uniform throughput distribution to eliminate cross-partition fan-out. | Uses low-cardinality keys (e.g. status or date strings), triggering the 20GB partition limit breach and hot-partition throughput starvation. | Omits partition key strategy during schema design, causing Cosmos DB to fall back on inefficient random partitions or single-partition bottlenecks. | Writes queries without partition key filters in the WHERE clause, triggering cross-partition fan-out queries that multiply RU consumption by partition count. |
| 429 RequestRateTooLarge Throttling Elimination & Client Retries | Eliminates HTTP 429 exceptions via server-side partition rebalancing, client SDK connection tuning (Direct Mode, TCP), custom exponential backoff policies, and batch bulk executor optimizations. | Relies entirely on default SDK retry policies, leading to client-side thread starvation, connection pool exhaustion, and end-user request timeouts. | Advises increasing provisioned RU/s limits as the only fix for 429 errors, dramatically inflating monthly Azure cloud spend. | Catches 429 exceptions in application code and retries immediately in tight loops, exacerbating cluster throttling storms. |
| Autoscale RU/s Capacity Rightsizing | Audits normalized RU/s utilization profiles across peak and off-peak hours, rightsizing autoscale maximum throughput and converting steady workloads to reserved capacity, with savings measured against the current bill. | Over-provisions manual RU/s capacity to avoid 429 alerts, leaving up to 70% of provisioned throughput unutilized during off-peak hours. | Configures unmonitored high autoscale ceilings with 10x dynamic scale headroom, triggering massive unexpected cloud billing spikes. | Operates in manual provisioning mode without workload profiling, oscillating between severe under-provisioning and costly over-provisioning. |
| Consistency Level Calibration (Strong, Bounded, Session, Eventual) | Mathematically evaluates consistency requirements across five tiers (Strong, Bounded Staleness, Session, Consistent Prefix, Eventual), optimizing session token propagation to balance latency and RU costs. | Configures Strong consistency globally across all containers, doubling write RU costs and incurring severe multi-region latency overhead. | Leaves all workloads on default Session consistency without understanding read-your-own-writes session token propagation across microservices. | Switches to Eventual consistency indiscriminately to save RU costs, introducing dirty reads and data anomalies in transactional workflows. |
| Multi-Region Multi-Master Active-Active Topology & Conflict Resolution | Architects multi-region active-active write topologies with custom conflict resolution policies (LWW timestamp vs merge Stored Procedures), designed around the availability and recovery targets agreed for the workload. | Relies on default Last-Writer-Wins (LWW) conflict resolution without custom conflict procedures, leading to silent data overwrites during concurrent cross-region updates. | Avoids multi-region deployments altogether due to complexity, leaving mission-critical systems vulnerable to single-region Azure datacenter outages. | Enables multi-region writes without scoping replication latency, triggering cross-region data sync races and bloated cross-region egress charges. |