Backfill Job Overwhelming Live Production Database Write Capacity

System Design Interview•~30 min read•medium

Data migration backfill script populating a new column across 100 million user rows.

1. Understand Requirements & Scope

Data migration backfill script populating a new column across 100 million user rows. Failure cascade dynamic: 100k QPS → TTL Expiration → Cache Miss Herd → Origin Slam → 💥 DB Meltdown.

Functional Requirements:

Operational Invariant: "Data backfill scripts must execute in small primary-key-bounded batches and throttle dynamically based on replication lag."
Production Hardening: Throttle backfill scripts dynamically: update records in small batches (e.g. 500 rows) based on primary key ranges ('WHERE id BETWEEN ? AND ?'), sleep 100ms between batches, and pa
Prevent cascading failure by isolating downstream degradation at the ingress boundary.

2. Back-of-the-Envelope Capacity Estimation

• Incident Scenario Baseline: Data migration backfill script populating a new column across 100 million user rows.

• Failure Cascade Path: 100k QPS → TTL Expiration → Cache Miss Herd → Origin Slam → 💥 DB Meltdown

• Sub-millisecond rejection / shed latency for overloaded requests

3. High-Level Architecture Flow

Throttle backfill scripts dynamically: update records in small batches (e.g. 500 rows) based on primary key ranges ('WHERE id BETWEEN ? AND ?'), sleep 100ms between batches, and pause automatically if database replication lag exceeds 1 second. Invariant: "Data backfill scripts must execute in small primary-key-bounded batches and throttle dynamically based on replication lag."

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

Fig 1. Architecture data flow and component topology.

4. Production Implementation & Code

// HARDENED: Fast local Bloom filter / Redis revocation list verification
Claims claims = Jwts.parser().setSigningKey(secret).parseClaimsJws(token).getBody();
if (revocationBloomFilter.mightContain(claims.getId()) && redis.exists("revoked:" + claims.getId())) {
    throw new SecurityException("Revoked token access attempt rejected");
}

Hardened Implementation Sequence

Ingress Boundary Defense: Throttle backfill scripts dynamically: update records in small batches (e.g. 500 rows) based on primary key ranges ('WHERE id BETWEEN ? AND ?'), sleep
Failure Containment: Eliminate unconstrained buffering and propagate physical backpressure.
Invariant Enforcement: Data backfill scripts must execute in small primary-key-bounded batches and throttle dynamically based on replication lag.

5. Key Decisions & Operational Mitigations

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.

Operational Hazards & Mitigations

•Cascading Failure: Running an un-throttled Python script: 'UPDATE users SET new_col = compute()'. The script updates 10,000 rows/sec, saturating database IOPS, pegging CPU at 100%, and causing live customer checkout transactions to time out.
•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.

Interactive Knowledge Check • Question 1 of 3↓

Interactive Practice Quiz•Question 1 of 3

intermediate

Canary vs Blue-Green Release Strategies

What is the key advantage of Canary Deployments over Blue-Green Deployments for large-scale microservice clusters?