← All Problemssystem-designhard~30 min

DynamoDB GSI (Global Secondary Index)

Backpressure Throttling Primary Table Writes High-write DynamoDB table with a Global Secondary Index (GSI) configured with lower WCU provisioning.

Scope, Requirements & Constraints

Backpressure Throttling Primary Table Writes High-write DynamoDB table with a Global Secondary Index (GSI) configured with lower WCU provisioning. Failure cascade dynamic: 100k QPS → TTL Expiration → Cache Miss Herd → Origin Slam → 💥 DB Meltdown.

Core Functional Requirements

✓Operational Invariant: "A DynamoDB GSI must have write capacity provisioned to match the primary table to prevent GSI backpressure write throttles."
✓Production Hardening: Provision GSI WCU capacity equal to or greater than the primary table's WCU, or use DynamoDB On-Demand capacity mode, and avoid GSIs on non-uniform or low-cardinality attributes.
✓Prevent cascading failure by isolating downstream degradation at the ingress boundary.

Scale & Latency Constraints

—Incident Scenario Baseline: Backpressure Throttling Primary Table Writes High-write DynamoDB table with a Global Secondary Index (GSI) configured with lower WCU provisioning.
—Failure Cascade Path: 100k QPS → TTL Expiration → Cache Miss Herd → Origin Slam → 💥 DB Meltdown
—Sub-millisecond rejection / shed latency for overloaded requests

Reference Architecture & System Blueprint

Provision GSI WCU capacity equal to or greater than the primary table's WCU, or use DynamoDB On-Demand capacity mode, and avoid GSIs on non-uniform or low-cardinality attributes. Invariant: "A DynamoDB GSI must have write capacity provisioned to match the primary table to prevent GSI backpressure write throttles."

System Architecture Blueprint

Production Topology

DynamoDB GSI (Global Secondary Index) Architecture Blueprint

Architecture Flow NarrativeIngress → Bounded Admission Controller → Adaptive Concurrency / Queue Gate → Protected Worker Engine; Overload Shed Path → HTTP 429 / Circuit Fallback (<0.1ms).

Hardened Implementation Steps

1Ingress Boundary Defense: Provision GSI WCU capacity equal to or greater than the primary table's WCU, or use DynamoDB On-Demand capacity mode, and avoid GSIs on non-uniform or
2Failure Containment: Eliminate unconstrained buffering and propagate physical backpressure.
3Invariant Enforcement: A DynamoDB GSI must have write capacity provisioned to match the primary table to prevent GSI backpressure write throttles.

Production Code Contrast & Implementation

java

// HARDENED: Error-handling deserializer with Dead Letter Queue (DLQ)
@KafkaListener(topics = "orders", errorHandler = "dlqErrorHandler")
public void onMessage(ConsumerRecord record) {
    try {
        OrderEvent event = serializer.deserialize(record.value());
        orderService.process(event);
        ack.acknowledge();
    } catch (DeserializationException de) {
        // Route poison pill immediately to DLQ without halting topic partition commit offset
        dlqProducer.send("orders-dead-letter", record.key(), record.value());
        ack.acknowledge();
    }
}

Key Decisions & Trade-Off Analysis

Architectural comparison of naive unconstrained allocations versus production-hardened mechanical sympathy.

Architectural Decisions & Trade-Offs

⚖Ingress Admission: Naive unconstrained buffering causes queue bloat and GC exhaustion. Mitigation: Bounded ingress gate with fast non-blocking shedding.
⚖Resource Strategy: Static capacity allocations collapse under brownouts. Mitigation: Dynamic adaptive limits scaling to real-time physical bounds.
⚖Outage Impact: Cascading lock convoys and memory saturation. Mitigation: Isolated failure domains keep P99 latency flat and protected.

Alternatives Evaluated

→Naive Approach: Primary table write traffic surges. The GSI exhausts its allocated WCU capacity. DynamoDB throttles writes on the primary table to allow the GSI to ca
→Production-Hardened Pattern: Provision GSI WCU capacity equal to or greater than the primary table's WCU, or use DynamoDB On-Demand capacity mode, and avoid GSIs on non-uniform or

Scale Bottlenecks & Operational Hazards

Operational Hazards & Mitigations

⚠Cascading Failure: Primary table write traffic surges. The GSI exhausts its allocated WCU capacity. DynamoDB throttles writes on the primary table to allow the GSI to catch up, failing primary user transactions.
⚠Breakdown Chain: 100k QPS → TTL Expiration → Cache Miss Herd → Origin Slam → 💥 DB Meltdown
⚠Shedding Failure: Without fast rejection at the boundary, queued dead work triggers multi-second GC pauses, CPU thrashing, and cascading 504 Gateway Timeouts.

Changed Constraints & System Extension

How does the system enforce physical resource boundaries under sudden downstream latency brownouts?

Extension Implementation Steps

1Track real-time latency gradients and inflight concurrency.
2Reject excess traffic at the ingress boundary within <0.1ms.
3Monitor P99 latency and verify autonomous recovery when downstream pressure subsides.

Follow-Up Trade-Offs

⚖Architectural Invariant: "A DynamoDB GSI must have write capacity provisioned to match the primary table to prevent GSI backpressure write throttles."
⚖Physical Resource Boundary: Dynamic admission control ensures worker threads never buffer dead requests during downstream brownouts.

Interactive Assessment & Knowledge Check

Test your understanding of the architecture decisions, data patterns, and trade-offs used in DynamoDB GSI (Global Secondary Index).

Interactive Practice Quiz•Question 1 of 3

advanced

Core Architectural Principles of B-Trees vs LSM-Trees Storage Engines

What is the primary benefit of applying B-Trees vs LSM-Trees Storage Engines in production systems?