Menu

8 system design flows interviewers ask you to draw, and the step they always poke at
📰

8 system design flows interviewers ask you to draw, and the step they always poke at

DEV Community: beginners·Mahesh·about 19 hours ago
#b6YpCVVo
#devtobeginners#devto#dev#cache#draw
Reading 0:00
15s threshold

Most system design rounds I've seen go wrong in the same place. Not the big boxes. The candidate draws a load balancer, a cache and a database, the interviewer nods, and then asks one small question about a single arrow: "what happens here when this fails?" That arrow is where the round is decided.

So here are eight flows that come up again and again, what to draw for each, and the one step interviewers almost always poke at. If you can walk through that step out loud, you're in good shape.

1. A request through a load balancer

Draw: client, DNS, load balancer, three app servers, a shared database.

The step they poke at: what the load balancer does when one server stops answering. Talk about health checks (how often, what counts as "unhealthy"), and what happens to requests already in flight on the dying server. Bonus: sticky sessions, and why they make scaling harder.

2.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.