HLD-127·Caching & Edge
Easy · 500 ptsE-Commerce Promo Code & Eligibility Rule Validator
Design a checkout promo-code eligibility service validating campaign rules, minimum cart thresholds, and merchant promo metadata during seasonal sales.
Max p99
≤ 38 ms
Availability
≥ 99.5%
Budget
≤ $2,950
Functional Requirements
- FR-1GET /promos/{promo_code}/validate — Evaluates campaign dates, cart eligibility, and discount rules.
- FR-2POST /promos — Publishes or pauses merchant promotional codes and logs redemptions.
- FR-3PATCH & DELETE /promos/{promo_code}/validate — Updates, revokes, or deletes promo_code entries with bounded TTL or explicit cache/index invalidation.
- FR-4Must sustain sub-40ms p99 cart checks during influencer promo drops and DB node failure.
Workload Profile
Baseline Cart Checks20,000 Read RPS / 1,800 Redemption Write RPS
Influencer Code Drop58,000 Read RPS / 5,000 Write RPS
Active Working Set8 GB active promo campaigns & eligibility rules
Traffic DistributionExtreme hot-key skew on viral promo_code strings
Consistency Model
Eventual campaign pause propagation (< 3s) for unlimited-use sitewide promo codes.
Relevant practice for
Solutions Locked
Sign in and either achieve AC or complete 3 official submissions on this question to inspect community diagrams and writeups.
Loading solutions...
Submission History (0)Select to replay
No submissions yet
Click Submit in the top bar to evaluate against all 7 judge cases and save each run here.
Click an item in Inventory above, or press B to add a component, double-click to name, C to connect.
Design Write-up
Write under ### Architecture for Diagram to take that up directly
Compulsory section · if not written yet, Diagram reads from the start of your write-up.
Architecture: required·FRs mentioned: 0/4·0 boxes · 0 edges
0 words