Code RoomGlobal secondary index geo-partitioned data
HardPrep Room Coding #3570

Global secondary index geo-partitioned data

System designDatabases & SQLConcurrencySenior–Staff~50 min

An e-commerce catalog is geo-partitioned: each product record is owned by the seller's home region and writes go there. But buyers need fast global query/filter across ALL products regardless of owning region — 'show electronics under $50 shipping to Germany', sorted, paginated, p95 < 150ms from any region. Building a synchronous global index on every write would couple write latency to all regions and create a write hotspot. Design a globally-queryable secondary index over data whose source-of-truth is partitioned by region. Address index freshness vs query latency, how a buyer query is fanned out or served, and what consistency a buyer can expect between the index result and the live product record (price/stock).

What a strong answer looks like

Clarify scale and constraints first. Propose a clean component breakdown, then go deep on the hard parts (data model, bottlenecks, consistency, failure modes) and name the trade-offs you are making.

Clarify5:30 left
Estimate5:30 planned
Design16:30 planned
Deep dive13:30 planned
Failure9:00 planned
0:00
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.