HLDArena
HLD-220·Storage & Media
Medium · 1,000 pts

Connected Vehicle OTA Firmware Rollout Manifests

Design an over-the-air (OTA) firmware ring-deployment manifest service polled by millions of connected vehicles during overnight charging windows.

Max p99
≤ 48 ms
Availability
≥ 99.5%
Budget
≤ $4,900

Functional Requirements

  • FR-1GET /ota/manifests/{vin_bucket} — Returns signed target firmware version and delta bundle URLs.
  • FR-2POST /ota/rings — Promotes or halts a canary firmware rollout ring and records install telemetry.
  • FR-3DELETE /ota/manifests/{vin_bucket} — Supports tenant retention TTL expiry, rule updates, or stream cleanup while keeping recent rollup caches fresh.
  • FR-4Must absorb synchronized overnight fleet polls and survive a 6x origin storage latency brownout.

Workload Profile

Daytime Polls36,000 Read RPS / 2,200 Telemetry Write RPS
Overnight Ring Surge108,000 Read RPS / 7,000 Write RPS
Active Working Set20 GB ring eligibility manifests & delta metadata
Traffic DistributionHeavy read concentration on active rollout vin_bucket rings

Consistency Model

Bounded eventual manifest propagation (< 10s) acceptable; rollout ring promotions and kill-switches stored durably.

Design Write-up
0 boxes · 0 edges
0 words
Hidden Cases #4–#7 run automatically on Submit
Case 1: Smoke & API ContractInput Workload
Read RPS
2,000 rps
Write RPS
220 rps
Key Distribution
Uniform (Low Skew)
Chaos Fault
None (Healthy Cluster)
Expected Pass CriteriaASSERTIONS
• Tail Latency: p99 ≤ 96 ms
• Availability: ≥ 99.5%
Valid end-to-end Client → Compute → Storage topology