A Conversation That Changed How I Think About Backend Systems - Part I
Me: I think our API servers will be the first thing to break if we get a million users. Him: Why do you think that? Me: Because… more users means more requests. The APIs will get overloaded, right? He smiled. Not the “you’re wrong” smile — the wait and think one. “Are the APIs really doing the work?” Him: When an API receives a request, what does it actually do most of the time? I paused. Me: It… validates input, runs business logic, calls the database, and returns a response. Him: Exactly. Now tell me — which part takes the longest? That’s when it clicked. Me: Waiting on the database. Him: Good. So if an API is slow, is it really the API that’s slow? The first bottleneck appears In large systems, API servers rarely struggle because of computation. They struggle because they wait . They wait for: Database queries Cache misses External services Network I/O At scale, waiting is more dangerous than working . “The database is the fragile one” Me: So the database is the real bottleneck? ...