What Is System Design And Why You Should Care

You're building an app. Writing one feature? Easy. But what happens when 10,000 people start using it at the same time? What happens when the database starts choking? What if one part crashes at 2am — does the whole app go down with it?

That's system design. Not the boxes and arrows people draw to look smart. It's just sitting down and asking yourself a few things before you touch the keyboard.

The Three Questions to Ask First

• Are people mostly reading data, or writing it? On Instagram, everyone's scrolling way more than posting.
• What's the one thing that would hurt the most if it broke? Build around protecting that.
• Can some data be a bit late, or does it need to be exact every second? Your follower count lagging a bit is fine. Your bank balance being wrong is not.

Two Engineers, Same Task

Two guys, same task — build a URL shortener.

First guy just starts typing code. One server, one database. Tests it with 5 friends, looks perfect, ships it.

Second guy thinks first. Realizes people will click links way more than create them, so he puts a cache in front of the database. Decides the link count showing up a bit late is fine, but the click counter can never be wrong. Then he builds.

Same deadline, same task. First guy's app dies the moment real traffic hits. Second guy's app doesn't even blink.

That's it, that's the whole thing. The diagram is just what's left over after you've made these calls, not where you start.

So tell me — you plan first, or you just start typing and fix it as it breaks?