YouTube ingests hundreds of thousands of hours of video a day and serves billions of watch sessions. A new engineer proposes that "the architecture" of YouTube is its choice of programming languages and frameworks. What is wrong with that framing, and what is the architecture actually?

What is being tested

Whether you can distinguish architecture from implementation using the only test that survives contact with a real system: the cost of changing your mind.

The reasoning

A language choice inside one service can be reversed by one team in one quarter, and nobody outside that team needs to be told. That is an implementation decision, however large the codebase.

Now consider the decisions that actually shape a video platform:

• Upload is decoupled from playback. A user's upload completes when bytes are durably stored, not when the video is watchable. Everything expensive — transcoding into a ladder of renditions, thumbnail extraction, content matching, captioning — happens asynchronously behind a queue.
• Storage is tiered by popularity, not by age alone. The overwhelming majority of the catalogue is watched rarely; a tiny fraction is watched constantly. One storage class for both is either ruinously expensive or unusably slow.
• The serving path is a CDN and the origin is a fallback. Playback traffic is not permitted to reach the storage layer in the common case.
• Metadata and media live in different systems with different consistency guarantees. A view count can be approximate and late. A video's privacy setting cannot.

Try to reverse any one of those and you are re-planning the whole platform. That is the signal.

The working definition

Architecture is the set of decisions that are (a) hard to reverse, (b) affect more than one team, and © determine whether the quality attributes can be met at all. Everything else is design, and design is allowed to be wrong for a while.

Why the wrong answer is tempting

The "technology stack" answer is common because a stack is visible — you can read it out of a repository. The decoupling of upload from playback is invisible in any single repository, which is precisely why it needs writing down.