A reader in Tokyo asks a library in Virginia for a page. The request crosses an ocean, the answer crosses it back, and no amount of clever engineering makes light travel faster. Latency is distance, and distance is the one enemy no server outsmarts. So you stop trying. Instead of making the reader come to the library, you open a branch in every town, stock it with copies of the most-asked pages, and let the reader walk next door. That is the last room of the systems-talking wing, and it is the one that stops fighting distance and simply moves the answer closer.

That branch network is a content delivery network, a CDN. The little branches are edge locations, caches scattered near where people live. A reader's request stops at the nearest one: a hit is already next door, and a miss makes the long trip back to the original, the origin, exactly once, then stocks the copy so the next neighbor never waits. If that sounds familiar, it should. It is the same hit, miss, and stale-copy bet from the cache room, drawn across the whole globe.

What the room teaches

The catch is the same one every cache has: a branch can drift from the original. You control that drift with a TTL, the time a copy is allowed to live before it is checked again, and CloudFront's default is 24 hours. When you push a new version, you either wait the TTL out, pay for an invalidation, or, for free, give the new file a new versioned name so nobody is ever handed yesterday's copy by accident. And the honest limit: shared, stable, read-heavy things like images, video, and static pages cache beautifully at the edge, while content that is unique to one person and must be correct to the second, a bank balance, a private feed, does not cache there at all.

The labels are worth locking. On AWS the CDN is CloudFront. Its frequently-confused cousin is Global Accelerator, and the one-line tell is that CloudFront carries copies while Accelerator clears the road. CloudFront works at layer 7, speaks HTTP, and caches. Global Accelerator works at layer 4, carries any TCP or UDP traffic, hands you two static IP addresses, and fails over between Regions in under thirty seconds without waiting on any DNS timer. So a game, a voice call, or a workload that needs a fixed IP for an allowlist points at Global Accelerator, not CloudFront. And the near-miss to refuse on the exam: routing each user to the Region that answers fastest is not the CDN, that is Route 53 latency-based routing, a different tool for a different job.

The wing, closed

The Outpost ends a five-room arc about how the parts of a system talk to each other without dragging each other down. The Book Drop and the Greeter were the two front doors, the async queue and the synchronous fleet, the ways a request arrives. The Breaker and the Allowance were the two shields, the way a system survives a failing dependency or a stampeding caller. And the Outpost is the reach, the move that carries the finished answer all the way out to the reader's door.

Look back and the whole wing rhymes. The queue's freedom to wait, the greeter's route-around-the-dead, the breaker's fast-fail, the allowance's steady drip, and now the edge's copy-next-door are five faces of one idea: stop making the other side wait on you. That is what a system that talks well actually is.

If you are just arriving, the map runs in order: the Data Wing on how distributed data behaves, then the coordination pair on how machines agree, then this wing, room by room on Learning Maps. And if you want the frame the whole series sits on, there is AWS is math and Kubernetes is physics.