| Single-Table Design & Composite Key (PK/SK) Modeling | Normalizes complex relational entity hierarchies into optimized single-table models using composite partition and sort keys (PK/SK), sparse indexes, and GSI overloading to serve the OLTP access patterns at single-digit millisecond p99 latencies. | Recreates traditional relational schemas across dozens of discrete tables, executing expensive application-side JOINs that multiply latency, compute overhead, and consumed request units across requests. | Treats DynamoDB like a relational SQL database; deploys one table per entity and defaults to unindexed, unbounded table Scan operations that stall during peak user traffic. | Defines ad-hoc key schemas without composite hierarchies or access pattern planning, frequently hitting partition limits and forcing full table scans for basic entity lookups. |
| Synthetic Suffix Sharding (1,000 WCU Partition Cap Elimination) | Identifies high-velocity write keys and designs deterministic or randomized synthetic suffix sharding (e.g. PK#001–PK#050) with scatter-gather parallel queries, permanently bypassing the strict 1,000 WCU per physical partition ceiling. | Attempts to fix 1,000 WCU partition throttles by globally increasing provisioned table WCU, multiplying AWS cloud bills while hot-partition throttling persists unchanged. | Blames DynamoDB engine constraints and bolts on slow external caching layers that introduce stale data inconsistencies and cache invalidation race conditions. | Unaware of the 1,000 WCU physical partition ceiling; directs high-velocity time-series or event streams to single monolithic partition keys, causing immediate P1 write throttling. |
| On-Demand vs Provisioned Autoscaling & Reserved Capacity Sizing | Analyzes CloudWatch consumed capacity distributions, burst profiles, and traffic histograms to calibrate auto-scaled provisioned capacity and commit to 1- or 3-year Reserved Capacity where the usage pattern supports it. | Leaves mission-critical tables in default on-demand mode permanently for operational simplicity, paying up to a 7x pricing premium on steady-state predictable workloads. | Configures rigid static provisioned capacity thresholds with disabled autoscaling, causing widespread throttling during sudden bursts and heavy over-spend during off-peak hours. | Switches capacity modes reactively based on sporadic billing alarms without calculating consumed capacity curves or commitment breakeven thresholds. |
| Global Secondary Index (GSI) Over-Provisioning & Write Amplification | Audits query projection attributes to engineer KEYS_ONLY or INCLUDE GSIs, preventing table-wide write throttling from unprojected GSI backpressure and minimizing storage write amplification. | Configures ALL attribute projections on every secondary index by default, multiplying table write amplification, storage volume, and cross-region replication expenses by 3x–5x. | Provisions redundant, overlapping GSIs for minor query variations without monitoring consumed index write capacity or index backpressure metrics. | Omits GSIs entirely or provisions inverted indexes that suffer from extreme partition key skew, throttling primary table write transactions during bursts. |
| Global Tables Multi-Region Active-Active Replication & OCC | Architects active-active multi-region Global Tables with deterministic conflict resolution, Optimistic Concurrency Control (OCC) attribute versioning, and real-time cross-region replication latency telemetry. | Enables Global Tables without OCC versioning or idempotency controls, resulting in silent data overwrites, race conditions, and last-writer-wins data corruption during concurrent cross-region updates. | Builds fragile custom application-tier replication microservices, leading to desynchronized regional datasets, split-brain states, and cascading reconciliation failures. | Deploys Global Tables across distant geographies without evaluating cross-region data transfer pricing amplification or eventual consistency read replication delays. |
| DynamoDB Streams & Poison-Pill Resilient Event-Driven Consumer Pipelines | Implements DynamoDB Streams with Kinesis Adapter and AWS Lambda consumers featuring exponential backoff, Dead Letter Queues (DLQ), and bisect-batch-on-error, so failed records are retried or captured in the DLQ instead of being dropped. | Attaches unmonitored Lambda functions directly to DynamoDB Streams without DLQs or error bisecting; a single malformed poison-pill record halts entire shard processing for hours. | Avoids native CDC Streams and runs scheduled cron scripts polling tables via scans, incurring massive RCU consumption and introducing multi-minute pipeline data lag. | Writes unhandled stream consumer functions that crash on schema variations, causing shard iterator expiration and permanent, silent event stream data loss. |