Vercel Made Crystal Clear · chapter 2: The Mental Model: Git Push to Served Request

Immutability and the alias pointer

2026-09-29

Three deployments, each permanent and independently reachable. Only the production domain moves. Rolling back never deletes or rebuilds anything, it just repoints the arrow.

Below: the paragraph from the book that builds this idea, then the diagram itself (Figure 2.2), and a recap. About a minute of reading.

Every deployment fans out into the same three serving surfaces (edge network, functions, ISR cache) whether or not any domain currently points at it. A deployment with no domain attached is still a complete, working, addressable thing at its own generated URL. That single fact is what Figure 2.2 makes visual.

Figure 2.2: Immutability and the alias pointer. Three deployments, each permanent and independently reachable. Only the production domain moves. Rolling back never deletes or rebuilds anything, it just repoints the arrow.
Figure 2.2: Immutability and the alias pointer. Three deployments, each permanent and independently reachable. Only the production domain moves. Rolling back never deletes or rebuilds anything, it just repoints the arrow.

Recap

  • The idea: Three deployments, each permanent and independently reachable.
  • The picture: Figure 2.2, from chapter 2 ("The Mental Model: Git Push to Served Request") of Vercel Made Crystal Clear.
  • Go deeper: the chapter builds this step by step, with recipes and sources at the end.

This diagram is one of many in Vercel Made Crystal Clear.

Every chapter opens with the gist, draws the hard ideas, and ends with recipes and sources.

Get the book

All diagrams