Fly.io Made Crystal Clear · chapter 2: The Mental Model: Deploy to Served Request
The full path from local code to a served request
2026-09-16
Build and release happen once per deploy. Anycast, the Fly Proxy, and your Machine happen on every request, and this is the diagram the rest of the book keeps zooming into.
Below: the paragraph from the book that builds this idea, then the diagram itself (Figure 2.1), and a recap. About a minute of reading.
Figure 2.1 puts the whole path on one page: your code going in at the top, a request being served at the bottom, and every stop in between. This is the hero diagram of the book. Chapters on deploys, machines, regions, and networking each zoom into one piece of it, so it is worth studying properly here.
Recap
- The idea: Build and release happen once per deploy.
- The picture: Figure 2.1, from chapter 2 ("The Mental Model: Deploy to Served Request") of Fly.io 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 Fly.io Made Crystal Clear.
Every chapter opens with the gist, draws the hard ideas, and ends with recipes and sources.
Get the book
