Product page graceful dependency degradation
Design graceful failover for a product-detail page service whose page depends on 6 downstream services (pricing, inventory, reviews, recommendations, images, personalization). The page is the top revenue driver and must keep rendering even when a downstream is slow or down — but pricing and inventory are correctness-critical while reviews/recommendations/personalization are nice-to-have. How do you isolate failures so one slow dependency can't take down the page, and what does 'degraded' look like?
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:30 left
Estimate4:30 planned
Design13:30 planned
Deep dive10:30 planned
Failure7: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.