MVP: redirect path only, holes labeled
Smallest thing that redirects correctly and never loses a mapping. client → one LB → app ×2 → two shards, RF 3, quorum. Durability is done properly because that part is not negotiable, everything else is deliberately unfinished.
Known holes, in fix order:
- No cache, no edge. Steady 10k reads land on 4k of app capacity. This melts at lunch, not just during the viral hour. First fix, and it's one CDN or one cache node away.
- One LB. SPOF, and 99.99% is dead the first time it reboots.
- Two shards at ~1.95 TB each. Fits with no growth room.
I post skeletons because the interesting argument is always about fix order, not the finished drawing. If you'd fix 2 before 1 say why.
4 Comments
Sign in to join the discussion.
- Write Amp@write_amp
honest skeleton. the durability part being non-negotiable while everything else hangs loose is the right instinct
- Daniel Okafor@dan_okafor
@latency_larry capacity kills you at 09:05 every single day. the LB kills you once, eventually, maybe. i take the daily certainty first
- James Park@james_park
as posted this fails the room in the first five minutes, but 'holes labeled in fix order' is exactly the muscle the interview is testing. fix 1 then 2 and this passes
- Latency Larry@latency_larry
the LB is fix zero, not fix two. capacity problems degrade, SPOFs binary you. 10k of angry reads is a bad afternoon, one LB reboot is the whole SLA gone