ORIGINAL SYSTEM DESIGN QUESTION
Auditable usage metering
Meter API consumption and produce monthly tenant invoices from usage events.
Original exercise · intermediate. Editorial role relevance does not imply a company has asked this question.
Requirements and constraints
- 100 million usage events/day; 100,000 tenants.
- Replays and late events must not silently double-bill users.
- State assumptions and justify security, cost, operational ownership and data retention.
Pressure round
A late usage batch arrives after an invoice was finalized.
Build and explain the design
Requirements & scope
Who uses it? What must it do? What is explicitly out of scope? State latency, durability and privacy goals.
Self-review guidance
Define the actors, required operations and out-of-scope behavior. Explicit requirement: Replays and late events must not silently double-bill users.
Capacity estimates
State assumptions, peak requests/second, data volume and retention. Show your arithmetic and units.
Self-review guidance
Use this workload: 100 million usage events/day; 100,000 tenants. Convert rates and payload sizes into peak compute/storage assumptions; show units, headroom and what remains unmeasured.
APIs & data model
Describe endpoints/events, entity keys, indexes, authorization, and idempotency.
Self-review guidance
Define usage event IDs, pricing revisions and invoice adjustment records.
Architecture & data flow
Describe components and request/event paths. Use plain text arrows to sketch your design; explain each responsibility.
Self-review guidance
Keep an immutable event ledger and reproducible billing projections.
Failures & observability
What happens on overload, duplicate events, partial failures or lost dependencies? Discuss monitoring and recovery.
Self-review guidance
Pressure-test: A late usage batch arrives after an invoice was finalized. Describe bounded recovery, deduplication, observability and a user-visible failure state.
Tradeoffs & alternatives
Compare two plausible approaches. State the costs, consistency model and what would make you change the design.
Self-review guidance
Compare invoice revisions with adjustment entries and reproducibility.
Design guidance describes assumptions and tradeoffs; no architecture has been simulated or benchmarked.
Practice this question
Save your work privately, explain decisions and return to your revision queue.
Open practice workspaceBrowse the question library →