Load Balancing and CDNs

Two networking tools sit at the front of almost every large online service: a load balancer and a CDN (Content Delivery Network). They solve different problems, but they often work together — one making sure no server gets overwhelmed, the other making sure users don't wait longer than necessary.

A good pair of analogies: imagine a busy restaurant with a host at the door who seats guests across all available tables, so no single waiter drowns while others are idle — that's a load balancer. Now imagine a restaurant chain with a branch in every neighborhood, so no customer has to drive across town — that's a CDN. One spreads the work; the other shortens the distance.

Together, they're the reason large websites stay fast and don't fall over when thousands of visitors arrive at once.

The Problem with One Server

Every server has a ceiling — a point beyond which it can't handle any more requests without slowing down or failing entirely. A single web server is also a single point of failure: if it crashes or needs maintenance, the whole service goes down. For a personal blog, that might be fine. For a shop that takes orders around the clock, it isn't. The solution to both problems — the capacity ceiling and the single point of failure — is to use more than one server. But then you need something in front of them to direct the traffic. That's the load balancer.

What a Load Balancer Does

A load balancer sits in front of a group of servers and acts as the single address that all incoming traffic hits. It receives each request and sends it to one of the servers behind it, spreading the work evenly. If one server becomes unavailable — because it crashed, or because it's being updated — the load balancer stops sending traffic to it and redirects to the others. Visitors don't notice; from their perspective, the service keeps running.

The load balancer doesn't serve the actual content itself. It directs traffic, the way a restaurant host seats guests — the host isn't the one cooking.

What a CDN Does

A CDN — Content Delivery Network — is a network of servers spread around the world in locations close to users. Instead of every request traveling all the way back to your main server (which might be in a data center on another continent), the CDN stores cached copies of your content — images, videos, static pages — in those nearby locations. When a user in Tokyo requests a page, they get the cached copy from a CDN location in Tokyo, not from a server in Virginia. The page loads in milliseconds rather than hundreds of milliseconds.

The CDN is not a backup of your servers; it's a caching layer. It stores copies of content that doesn't change often, and it refreshes those copies when the original is updated. Dynamic content — a personalized shopping cart, a live score — still goes back to your main servers; the CDN serves the static, shareable parts.

Load Balancer and CDN Together

In a well-designed system, both layers work at once. A CDN handles the static content that can be served from nearby — images, CSS, videos — reducing load on the main servers and making the response feel instant for users anywhere in the world. The load balancer handles the remaining dynamic requests, spreading them across several servers so no one machine gets overwhelmed. Each tool reduces a different kind of pressure, and together they make a service that can handle large audiences without falling over.