1.1 The Big Picture
What actually happens between pressing Enter and seeing the UI.
When a user opens https://app.example.com, a lot happens before any of your
code runs. Most infrastructure knowledge is just filling in this diagram.
Diagram source
flowchart TD
A[User Browser]
B[DNS]
C[CDN / Edge]
D[Load Balancer]
E[Frontend Server]
F[API Gateway]
G[Backend Services]
H[Database]
A --> B
B --> C
C --> D
D --> E
E --> F
F --> G
G --> HEach box is a place where the request can be cached, redirected, rejected, rewritten or dropped. Each box also logs separately, which is why "the site is broken" is not a debuggable statement until you know which hop failed.
The request lifecycle
In more detail, with the browser doing most of the work:
Diagram source
sequenceDiagram
participant U as User
participant B as Browser
participant DNS as DNS Server
participant CDN as CDN
participant APP as Application
participant API as API
U->>B: Open app.example.com
B->>DNS: Resolve domain
DNS-->>B: Return IP
B->>CDN: HTTPS request
CDN->>APP: Forward request if needed
APP-->>B: HTML / JS / CSS
B->>API: Fetch data
API-->>B: JSON response
B-->>U: Render UINote the shape of it. The browser makes two distinct kinds of request: one for the documents and assets, one for data. They often travel different paths, hit different caches and fail for different reasons. A page that renders but shows no data has a working delivery path and a broken API path — already half the debugging done.
The interview question that is actually useful
What exactly happens after I type a URL and press Enter?
This is a cliché interview question, and it is also the single best organizing question for infrastructure. A complete answer touches DNS, TCP, TLS, HTTP, caching, proxies, rendering and the browser's own networking — which is most of this chapter and the next.
You are not expected to answer it fully yet. Come back to it after Caching and see how much more of it you can fill in.
Where things go wrong
A rough map of which layer owns which symptom:
| Symptom | Usually owned by |
|---|---|
| Domain does not resolve at all | DNS |
| Certificate warning in the browser | TLS |
| Old JavaScript after a deploy | Caching / CDN |
| 502 / 504 errors | Reverse proxy or upstream app |
| CORS error | The API's response headers |
| Works locally, fails deployed | Environment config |
| Logged out on every other request | Load balancer / session handling |
That table is worth more than it looks. Most of the time spent on an incident is spent deciding which box to open.