E-commerce index strategy
Design the indexing strategy for an e-commerce orders table (2 billion rows, 25k writes/sec) that must serve several query shapes fast: filter by customer_id + date range, filter by status + warehouse, full-text search on product name, and a dashboard counting orders per status per hour. Adding indexes blindly is killing write throughput. How do you choose which indexes to build, order their columns, and avoid index bloat?
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.
Clarify4:00 left
Estimate4:00 planned
Design11:30 planned
Deep dive9:30 planned
Failure6:00 planned
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.